Re: conflict of building XML::Xerces-2.5.0-0 using Xerces-C-2.6.0

"Lincoln A. Baxter" <[email protected]> writes:

> What is involved in make a new Xerces release for each release of
> Xerces-C?  Is it something we would work on scripting, so that we would
> not have to redo it with every release?

In a perfect world, it would simply be a matter of running SWIG
against the new header files, running the regression tests, and
rolling the tarball.

Usually, it involves a small amount of tweaking. For example, often
there are new header files in Xerces-C that must be added to the
Xerces.i interface file used by SWIG.

However, there is currently a horrendous memory leak inside XML-Xerces
at the moment. I did some experiments and couldn't locate the source,
but it wasn't Xerces-C. I re-wrote the Xerces.i interface file to only
use the basic Xerces-C components and the memory lead was gone. So I
haven't wanted to make any new releases until the Xerces.i interface
file could be re-written without the memory leak.

Cheers,
jas.