[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Classpathx-discuss] Re: LibxmlJ formalities
From: |
Nic Ferrier |
Subject: |
Re: [Classpathx-discuss] Re: LibxmlJ formalities |
Date: |
28 Feb 2003 00:36:09 +0000 |
Julian Scheid <address@hidden> writes:
> Tom Tromey wrote:
> > Usually I find that compiling from .java is worse, since the parser
> > (well, really the analysis phase) has a lot of bugs and oddities. I
> > know there are some bugs reading bytecode, though. I'm wondering if
> > you ran into those, or if you've found new ones...
>
Julian replied:
> Funny, it really turned out the exact opposite for me. Hmm. Well, gcj's
> compile-time behaviour is not very predictable, but at least the
> run-time behaviour of the stuff produced by it is...
Tom, is this true? I've been told in the not too distant past that
compiling from source was more reliable than from bytecode (by Per I
think).
Nic
- Re: [Classpathx-discuss] Re: LibxmlJ formalities, (continued)
- Re: [Classpathx-discuss] Re: LibxmlJ formalities, Nic Ferrier, 2003/02/25
- Re: [Classpathx-discuss] Re: LibxmlJ formalities, Julian Scheid, 2003/02/26
- Re: [Classpathx-discuss] Re: LibxmlJ formalities, Nic Ferrier, 2003/02/26
- Re: [Classpathx-discuss] Re: LibxmlJ formalities, Julian Scheid, 2003/02/26
- Re: [Classpathx-discuss] Re: LibxmlJ formalities, Nic Ferrier, 2003/02/26
- Re: [Classpathx-discuss] Re: LibxmlJ formalities, Julian Scheid, 2003/02/26
- Re: [Classpathx-discuss] Re: LibxmlJ formalities, Tom Tromey, 2003/02/26
- [Classpathx-discuss] Re: LibxmlJ formalities, Julian Scheid, 2003/02/26
- Re: [Classpathx-discuss] Re: LibxmlJ formalities, Tom Tromey, 2003/02/26
- Re: [Classpathx-discuss] Re: LibxmlJ formalities, Julian Scheid, 2003/02/26
- Re: [Classpathx-discuss] Re: LibxmlJ formalities,
Nic Ferrier <=
- Re: [Classpathx-discuss] Re: LibxmlJ formalities, Tom Tromey, 2003/02/27
Re: [Classpathx-discuss] Re: LibxmlJ formalities, David Brownell, 2003/02/25