Re: Expat with UTF-32 support (as implemented in

Jeremy Kloth wrote:

>One idea to solve this constant PITA wrt mod_python/apache would be a way to 
>define a "prefix" for all exported symbols.  So, for example in expat.h, 
>instead of:
>
>XMLPARSEAPI(XML_Parser)
>XML_ParserCreate(const XML_Char *encoding);
>
>it could be something like:
>
>XMLPARSEAPI(XML(Parser))
>XML(ParserCreate)(const XML_Char *encoding);
>
>where:
>
>#define XML_PREFIX XML
>#define XML(name) XML_PREFIX#_#name
>  
>
Jeremy,

are there any drawbacks to this?

I also seem to rememeber we once discussed a related issue on the list
where there was a need to have both versions of libexpat (UTF-8 and UTF-16)
loaded at the same time. This is not an issue on Windows, but apparently 
on Linux.

If we do anything about the above, we should cover the old issue as well.
However, for details I have to defer to those who are more knowledgable 
on Linux.

Since Fred (the Expat team leader) seems to have dropped out of sight, I 
would be
willing to commit a solution that is agreed upon by a group of knowledgable
Linux/Expat users like yourself, even if I don't completely understand it.

Karl