You are viewing a plain text version of this content. The canonical link for it is here.
Posted to j-dev@xerces.apache.org by Andy Clark <an...@apache.org> on 2000/09/06 20:01:08 UTC
[Xerces2] Docs: Crimson vs. Xerces
I hate using "vs" in the title since it's not a versus situation
at all. I spent some time looking at the Crimson code in CVS and
wrote up some points that evaluate both Crimson *and* the current
Xerces code base. I make some general good and bad comments about
both parser designs so that we have a better understanding of
where we can borrow ideas and code for Xerces 2.
As a reminder, all of these docs are part of the documentation
we're doing for a Xerces 2 concept implementation. And there
will be more coming in the near future.
If you want to read over any of the documentation or get involved
with this effort, first go to the web page and check it out.
http://www.apache.org/~andyc/xerces2/
--
Andy Clark * IBM, JTC - Silicon Valley * andyc@apache.org
Re: [Xerces2] Docs: Crimson vs. Xerces
Posted by James Duncan Davidson <du...@x180.com>.
on 9/6/00 11:01 AM, Andy Clark at andyc@apache.org wrote:
> I hate using "vs" in the title since it's not a versus situation
> at all. I spent some time looking at the Crimson code in CVS and
> wrote up some points that evaluate both Crimson *and* the current
> Xerces code base. I make some general good and bad comments about
> both parser designs so that we have a better understanding of
> where we can borrow ideas and code for Xerces 2.
Nice start at writing up what's good and bad in each. I don't have any
qualms with what's written up so far.
.duncan