"Lincoln A. Baxter" <[EMAIL PROTECTED]> writes: > Since we are appreciating... let me add my appreciation. > > At work (A major Financial Institution) we are using XML-Xerces (where > before we had used expat), because we wanted a _validating_ parser, for > a particular project. It worked great. It was only a minor annoyance > that the current version is 'old' (2.3).
Hi Lincoln, Thanks! It's great to know that it is being used! Honestly, it is dificult for me at times to continue with the project - I feel like I am the only person interested in it - I know this is *not* true - without help from many people we would not have the system working on Windows or OS X, for example. So knowing that people use XML-Xerces and want to see it continued really helps. > At home, I created and submitted a Gentoo Linux portage ebuild for > XML-Xerces, but by the time they got around to looking at it, their > standard Xerces (had moved on to 2.4), and it would nolonger build > without a downgrade, so they rejected it with the note I that I could > reopen the bugzilla ticket, if I had an ebuild that would work against > 2.4. or 2.5. I had to hack my system to keep portage from upgrading > Xerces (and breaking XML-Xerces). So I would love to see a version > built against a more recent xerces-c. I promise that I will upgrade the > ebuild, and resubmit, if an new version is made available. In the meantime, I *did* release a version of XML-Xerces for 2.4, and I put it in the nightly builds section of the download page. If you search the mailing list archives you should find a few messages with the URL if you can't find it on your own (my 'net connection is down at the moment, so I can't find it for you). > What is left to do? There are a few issues. This is the long term list: 1) Get 2.5 building out of the box. Right now there are two methods being wrapped by SWIG that won't compile - I need to add an %ignore directive so that SWIG skips those two methods. This *should* be simple, but I wasn't able to do it in the short time I had available. 2) Fix the *huge* memory leaks. XML-Xerces needs to be usable for long-running processes like mod_perl, and there are huge leaks coming from somewhere. If someone with valgrind or purify can locate these I will patch them. 3) Fix the horrible icky multiple inheritance hack I added for 2.0 to make the DOMNode hierarchy work properly. I need the help of someone who is more C++ savvy than I am to debug why the SWIG wrapping of the multiply inherited DOMNode methods are breaking unless I do an icky pointer cast from Perl. 4) Document the system. The only documents are the Doxygen C++ docs. Most Perl programmers shouldn't be forced to learn C++ to fully understand the system. For the short term, only 1) needs to be done. For the medium term 1) and 2) need to be done. Cheers, jas. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
