From: Thomas J. <tho...@in...> - 2005-06-17 07:39:18
|
Good morning, On Friday 17 June 2005 09:34, Christophe de VIENNE wrote: > > > > >>I implemented the code like I wrote above. And it works :-) > > > > >>It's not ABI compatible as the new library doesn't contain the > > > > >> static init object, but it's 100% API compatile. -> It's best to > > > > >> bumb the .so version for the next release. > > > > > > > > > > That would be highly undesirable. ABI compatibility must be > > > > > maintained until we have a really good reason to break it. > > > > > > > > What is holding you back from making the global init object do > > > > strictly nothing, so its only purpose is to keep ABI compatibility > > > > and users may or may not use it in their application ? > > > > > > > > Then, you are ready to remove it when you have other reasons to break > > > > ABI compatibility. > > > > > > This is a great idea. I'll cook up a new version of the patch the next > > > days. > > > > I was typing faster than thinking... doing nothing is not possible > > as libxml2 needs to be initialized. IMHO there is no ABI compatible > > way of replacing the global initialization code, is there? > > I think so, with the global init doing nothing IF an environnement variable > "LIBXMLPP_NO_STATIC_INIT" has been defined. This still requires recompilation and is therefore not ABI compatible, IMHO. Cheers, Thomas |