Hi All,

The Good News
--
I'm making a shapshot available for testing. It includes all API
components that were present in 2.5 - and I'm happy to add that all
known memory leaks are gone. Further testing may reveal some, but I
now understand enough of the issues that I am confident I can solve
them easily.

The Rest
---
There is one major problem with the snapshot - all DOMException and
SAXException classes will cause segfault if any attempt is made to
access their internal attributes (e.g. through a getMessage() or
getCode() call). This is a serious problem and needs to be fixed, but
while I'm tracking it down, the code is complete enought and robust
enough for others to test. So expect some failures in make test.

What it includes
--
I've include a file that documents which parts of the Xerces-C++ API
have been included (which header files have been wrapped). If you need
access to some part of the API that I haven't yet exposed, please
explain why you need it, and I'll be happy to include it.

What it doesn't include
--
The current code comes to around 78k lines - so I've made every effort
to exclude pieces of the API that I consider unnecessary in an attempt
to reduce the footprint of the code (see the file interface/ignore.i
if you want to see what parts of the API I've excluded).

How to get it
--
I've had some trouble uploading to apache, so I'm making the snapshot
and the digital signature temporarily available here:

  http://www.openinformatics.com/XML-Xerces-2.6.0-2005-05-28.tar.gz
  http://www.openinformatics.com/XML-Xerces-2.6.0-2005-05-28.tar.gz.asc

Please let me know if you can successfully compile on your favorite
platform/perl combo.

Please let me know if I've forgotten something (your favorite feaure,
the patch you emailed me 26 years ago, etc).

Please let me know if you have any difficulties.

Last but not least: Enjoy!

Cheers,
jas.

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to