This is the mail archive of the
mailing list for the GCC project.
Re: Minimal GCC/Linux shared lib + EH bug example
- From: loewis at informatik dot hu-berlin dot de (Martin v. L÷wis)
- To: Mark Mitchell <mark at codesourcery dot com>
- Cc: "Ralf W. Grosse-Kunstleve" <rwgk at cci dot lbl dot gov>, c++std-ext at research dot att dot com, gcc at gcc dot gnu dot org
- Date: 16 May 2002 12:34:12 +0200
- Subject: Re: Minimal GCC/Linux shared lib + EH bug example
- References: <5040000.1021522583@localhost>
Mark Mitchell <firstname.lastname@example.org> writes:
> It occurs to me that another way to solve these problems is to change
> the rules for loading modules, from the point of view of Python. The
> whole point of using RTLD_LOCAL is to prevent name clashes between
> Why not define that problem away?
> If the rule was that, for example, all externally visible names in the
> loaded modules had to be within namespaces that were assigned by some
> naming authority, or otherwise consistent, then you could load modules
> with RTLD_GLOBAL.
> Yes, I know this is non-trivial, but if you want to use C++, it's the
> practical solution over the medium term.
That indeed is an option: with sys.setdlopenflags, the application can
override Python's default of RTLD_LOCAL.