From: Ben Elliston <bje@redhat.com>
To: Mo DeJong <mdejong@cygnus.com>
Cc: <sourcenav@sourceware.cygnus.com>
Subject: Re: Java hiccups
Date: Mon, 15 Jan 2001 18:16:00 -0000 [thread overview]
Message-ID: <Pine.LNX.4.31.0101161314220.23569-100000@moshpit.cygnus.com> (raw)
In-Reply-To: <Pine.SOL.3.91.1010115162757.2740B@cse.cygnus.com>
mdejong wrote:
We are talking about the "right" way to fix it but it is going to
require some work. The GCJ based parser would work for Java code that
would compile, but fuzzy Java parsing is a much harder problem.
Having had a couple of years to ponder this issue, I'm coming to the
conlusion that perhaps the correct parsing of correct programs should come
before the best-effort parsing of incorrect programs. Perhaps fuzzy parsing
should take a back seat?
Ben
next prev parent reply other threads:[~2001-01-15 18:16 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-01-06 7:57 h j
2001-01-15 16:32 ` Mo DeJong
2001-01-15 18:16 ` Ben Elliston [this message]
2001-01-15 18:20 ` Mo DeJong
2001-01-15 19:16 ` Crazy Ideas Was: " Timothy M. Shead
2001-01-15 19:36 ` Ian Roxborough
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=Pine.LNX.4.31.0101161314220.23569-100000@moshpit.cygnus.com \
--to=bje@redhat.com \
--cc=mdejong@cygnus.com \
--cc=sourcenav@sourceware.cygnus.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).