http://devresource.hp.com/STK/impacts/i720.html

``Filtered Libraries: Filtered shared libraries divide up a large library
  into one filter and several implementation libraries. The user links
  against the filter library, but the real definitions of data and
  functions actually resides in the implementation libraries.  At run
  time, only those implementation libraries that are actually used are
  loaded. Filtered libraries can be nested; an implementation library can
  itself be a filtered library containing other implementation libraries.''

http://docs.hp.com/hpux/onlinedocs/B2355-90730/00/00/44-con.html

``Filtered shared libraries allow developers to reduce the memory
  footprint of their shared libraries by providing for deferred loading
  of shared libraries (load-on-bind, referred to as ``lazy loading'').
  Filtering divides up a large library into one filter and several
  implementation libraries.''

Sounds like a cool idea, does ld.so already do this?

Ben
-- 
"All men by nature have a desire to know." --Aristotle