>As the original author and architect of Xerces C++, I'm probably to blame
> for everything :-)
If you didn't hate most of your old code, I would doubt your credentials. I
certainly hate most of mine.
For my needs, it's been fine. The XMLCh thing sucks, but we all know the
history, and I ki
As the original author and architect of Xerces C++, I'm probably to blame for
everything :-) Though, as mentioned, this was like 1998'ish, and a lot of spilt
milk has passed under the bridge since then. Oh, to be able to go back and
spill it again, and this time have my stock options vest BEFORE
>I don't want to sound too negative here. Xerces-C++ has served the world
> well, was pioneering in its time, and will continue to serve its existing
> users
> for time to come. But I think we also need to be honest and realistic about
> the status of the project today, and let it be retired
Dear all,
We had a similar conversation to this on the Xalan mailing list a few months
back:
https://lists.apache.org/list?d...@xalan.apache.org:2022-6 (Future of Xalan-C)
https://lists.apache.org/list?d...@xalan.apache.org:2022-7 (Retire Xalan to the
Attic) [Xalan-J]
In both cases there was
