On Thu, 17 Jun 2004, Jason E. Stewart wrote:

> 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.

It would also be great to find out why exception handling does not operate 
reliably under AIX.  It is not a showstopper for daily use (or, at least, 
has not been to date) but results in chronic regression test failures.

I have taken several time-consuming stabs at isolating the problem, but 
have run into serious difficulties in getting the AIX debugger to load and 
trace test execution.  If anyone from IBM compiler tools feels motivated, 
I think this needs someone a bit more clueful than I working at it.

Otherwise, I'll add my voice to those thanking Jason for his tireless 
work.  A hearty "Way to Go!".

Steve


-- 

--------------------------------------------------------------------
Opinions expressed in this message are mine personally, not those of 
my employer.
--------------------------------------------------------------------


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

Reply via email to