grooke@tcom.stc.co.uk (Gill Rooke) (05/03/91)
I have heard it said that libraries like NIHCL, which require most classes to be in a tree headed by class <object>, create problems. Additional memory occurs for the classes largely because of the additional functionality required. For each object, there are a couple of items of data. How serious is this effect when applied to large systems? There is also a reported problem concerning some form of conflict, particularly when there are several large users of container classes. Maybe this only applies when working with external windowing packages etc.. Someone said ti only applied when more than two normally compatible packages are used. Any offers? Thanking you in anticipation Gil Rooke.