Re: python and its dlopen implementation

[prev] [thread] [next] [lurker] [Date index for 2006/01/31]

From: Phil Pennock
Subject: Re: python and its dlopen implementation
Date: 11:29 on 31 Jan 2006
On 2006-01-25 at 12:58 +0000, Simon Wistow wrote:
[ RTLD_GLOBAL not in python ]
> I'm sure there are reasons why not doing this is the default and,

Software hate of mine: RPC libraries which include some cryptographic
checksums which are almost-MD5 but called MD5.  MD5 with a different
initialisation vector.  But the internal library uses the same function
names as the standard ones.

So to get working MD5, either mess with the semi-automatic ordering of
the libraries in the make(1) rules (oh yay, more fragility) or it's
necessary to pull the RFC code into my_* routines and #define the
regular names in a header, to make the project build again on a platform
using that particular stack.

I think that this was part of the Transarc DCE libraries, but it might
have been another one, it's been a decade and the hate for DCE still
lingers, festering, in my soul.  DCE has many hates.  It took SOAP for
me to finally grudgingly admit DCE's good points.

And that's just with regular build-time linkage.

So yes, I can see why something working to the limited model of dlopen()
would leave RTLD_GLOBAL off by default.  ;^)  RTLD_CHILD_VISIBLE would
be a reasonable default, if it existed, but chasing down pollution of
"standard" names in the global namespace from every little twerp writing
some weird little c00l corner-case plugin for an esoteric library and
dicking with things they don't understand would take more time and cause
more hatred.
-- 
I am keeping international relations on a peaceable footing.
You are biding your time before acting.
He is coddling tyrants.
 -- Roger BW on topic of verb conjugation

Generated at 18:00 on 31 Jan 2006 by mariachi 0.52