Neil Heller wrote in a message to Roy J. Tellason:

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? I would 
RJ> have thought that this was a matter for the linker to determine.

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

I wasn't aware of that.  In the case of the stuff I use here (linux),  the
sources to the libraries are mostly available,  if you want them.

---