From: Anthony Green <green@redhat.com>
To: paul taney <paultaney@yahoo.com>
Cc: antlr-interest@yahoogroups.com, rhug-rhats@sources.redhat.com
Subject: Re: GCJ
Date: Mon, 14 Jul 2003 16:19:00 -0000 [thread overview]
Message-ID: <1058199588.3331.104.camel@escape> (raw)
In-Reply-To: <20030712171415.47625.qmail@web80602.mail.yahoo.com>
On Sat, 2003-07-12 at 10:14, paul taney wrote:
> Ric wrote:
> ...If I make a redhat 9 rpm I hope it can use
> the
> redhat installed gcj.so, probably it's also possible
> to compile it
> staticaly (or only do gcj.so statically). And what's
> 2.6 Mb nowadays ;)
> Advantage of using gcj is that it comes default
> nowadays with most linux distributions
FWIW, I used antlr on regular basis with gcj (and gij).
If I could change one thing about antlr, I would try to make a cleaner
separation between the build- and run-time classes. Right now they are
all in one package. Moving the runtime classes into a different
package, say antlr.runtime, would make life easier for gcj users. Once
done, we could build and use lib-antlr-runtime.so. There's no obvious
way to build nice shared libraries without this separation. You either
put everything into one .so, or you do some thing weird.
BTW - I was looking at how ant uses antlr. It looks like it spawns a
new java process. Why does it do this instead of just loading the
classes and running in-process?
> green@redhat.com is an antlr user, and he might
> upload an RH9 executable or help you make an rpm.
> I'll cross-post.
Well, to be clear, these days I just run antlr with "gij" instead of
"java", and then I link native versions of the runtime classes into my
app. Here's the list...
ANTLR_SOURCES = \
antlr-2.7.2/antlr/ANTLRException.java \
antlr-2.7.2/antlr/ANTLRHashString.java \
antlr-2.7.2/antlr/ANTLRStringBuffer.java \
antlr-2.7.2/antlr/ASTFactory.java \
antlr-2.7.2/antlr/ASTNULLType.java \
antlr-2.7.2/antlr/ASTPair.java \
antlr-2.7.2/antlr/BaseAST.java \
antlr-2.7.2/antlr/ByteBuffer.java \
antlr-2.7.2/antlr/CharBuffer.java \
antlr-2.7.2/antlr/CharFormatter.java \
antlr-2.7.2/antlr/CharQueue.java \
antlr-2.7.2/antlr/CharScanner.java \
antlr-2.7.2/antlr/CharStreamException.java \
antlr-2.7.2/antlr/CharStreamIOException.java \
antlr-2.7.2/antlr/CommonAST.java \
antlr-2.7.2/antlr/CommonToken.java \
antlr-2.7.2/antlr/DefaultFileLineFormatter.java \
antlr-2.7.2/antlr/FileLineFormatter.java \
antlr-2.7.2/antlr/InputBuffer.java \
antlr-2.7.2/antlr/LLkParser.java \
antlr-2.7.2/antlr/LexerSharedInputState.java \
antlr-2.7.2/antlr/MismatchedCharException.java \
antlr-2.7.2/antlr/MismatchedTokenException.java \
antlr-2.7.2/antlr/NoViableAltException.java \
antlr-2.7.2/antlr/NoViableAltForCharException.java \
antlr-2.7.2/antlr/Parser.java \
antlr-2.7.2/antlr/ParserSharedInputState.java \
antlr-2.7.2/antlr/RecognitionException.java \
antlr-2.7.2/antlr/SemanticException.java \
antlr-2.7.2/antlr/StringUtils.java \
antlr-2.7.2/antlr/Token.java \
antlr-2.7.2/antlr/TokenBuffer.java \
antlr-2.7.2/antlr/TokenQueue.java \
antlr-2.7.2/antlr/TokenStream.java \
antlr-2.7.2/antlr/TokenStreamException.java \
antlr-2.7.2/antlr/TokenStreamIOException.java \
antlr-2.7.2/antlr/TokenStreamRecognitionException.java \
antlr-2.7.2/antlr/TreeParser.java \
antlr-2.7.2/antlr/TreeParserSharedInputState.java \
antlr-2.7.2/antlr/collections/AST.java \
antlr-2.7.2/antlr/collections/ASTEnumeration.java \
antlr-2.7.2/antlr/collections/impl/ASTArray.java \
antlr-2.7.2/antlr/collections/impl/ASTEnumerator.java \
antlr-2.7.2/antlr/collections/impl/BitSet.java \
antlr-2.7.2/antlr/collections/impl/IntRange.java \
antlr-2.7.2/antlr/collections/impl/Vector.java \
antlr-2.7.2/antlr/collections/impl/VectorEnumerator.java
AG
--
Anthony Green <green@redhat.com>
Red Hat, Inc.
prev parent reply other threads:[~2003-07-14 16:19 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-12 17:14 GCJ paul taney
2003-07-12 17:23 ` GCJ paul taney
2003-07-14 16:19 ` Anthony Green [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1058199588.3331.104.camel@escape \
--to=green@redhat.com \
--cc=antlr-interest@yahoogroups.com \
--cc=paultaney@yahoo.com \
--cc=rhug-rhats@sources.redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).