This is the mail archive of the
java@gcc.gnu.org
mailing list for the Java project.
Re: SAX inclusion in libgcj
- From: nferrier at tapsellferrier dot co dot uk
- To: tromey at redhat dot com
- Cc: nferrier at tapsellferrier dot co dot uk, java at gcc dot gnu dot org
- Date: 26 Nov 2002 09:29:10 +0000
- Subject: Re: SAX inclusion in libgcj
- References: <u7kgamu62.fsf@tapsellferrier.co.uk><87d6ot3y97.fsf@fleche.redhat.com>
Tom Tromey <tromey@redhat.com> writes:
> >>>>> "Nic" == Nic Ferrier <nferrier@tapsellferrier.co.uk> writes:
>
> Nic> I've mentioned a couple of times that the ClasspathX project has a
> Nic> full JAXP implementation (apart from the XSLT). Should we include a
> Nic> regular feed of GNUJAXP in GCJ?
>
> All other things being equal, I think we should prefer GNU
> implementations to non-GNU ones.
>
> Are all other things equal? I don't really know the SAX code. Could
> you compare and contrast the GNU implementation with the one currently
> in the tree?
A couple of clarifications here:
1. The SAX API code is importable anywhere because it's free.
2. (c) assignment of SAX API is (I believe) unrealistic because a lot
of different people have hacked on it.
3. You guys have the SAX code, but not JAXP interfaces or an
implementation.
4. ClasspathX has an implementation and the SAX and DOM API
interfaces, with the exception licence.
I don't believe these things should be in the GCJ tree. It's just
marketing that does that surely? Is there some way we could offer
bundled versions (like Sun do) but not tie them completly together?
> Nic> PS why does fastjar not work with the libgcj jar file?!
>
> How does it not work?
Haven't had time to submit a bug report... I'll get round to it.
Nic