NH> What's different about a library in *NIX that makes it
NH> dynamically  loadable?  What sets a dynamically loadable
NH> library apart from any other  in *NIX?  How can a programmer
NH> know in advance that this option is  available?

RJ> What suggests that it's a function of the library involved? 
RJ>  I would have thought that this was a matter for the linker 
RJ> to determine.

The library must have entry points which are accessible to and known by 
the program calling them.  One of Microsoft's methods of forcing 
developers to buy new software is by changing entry identifiers.

þ CMPQwk 1.42 999

--- Maximus/2 3.01