At 09:59 PM 3/8/00 -0500, Johnny C. Lam wrote:
>Is there a more portable C construct to ensure that a function is
>called when a shared library is loaded, much like a global static C++
>object's constructor?

(OFF TOPIC REPLY ALERT!!!)

I may be misremembering, but I thought that, while the original C++
guaranteed execution of constructors for global objects, that they later
removed that guarantee (and that, as a matter of fact, many implementations
of C++ don't do it). Someone straighten me out. Have I gone senile before
40?