This is the mail archive of the
java-prs@sourceware.cygnus.com
mailing list for the Java project.
gcj/59
- To: apbianco at cygnus dot com
- Subject: gcj/59
- From: Tom Tromey <tromey at cygnus dot com>
- Date: 4 Oct 1999 20:20:00 -0000
- Cc: java-prs at sourceware dot cygnus dot com,
- Reply-To: Tom Tromey <tromey at cygnus dot com>
The following reply was made to PR gcj/59; it has been noted by GNATS.
From: Tom Tromey <tromey@cygnus.com>
To: Anthony Green <green@cygnus.com>
Cc: Java Gnats Server <java-gnats@sourceware.cygnus.com> ,
Alexandre Petit-Bianco <apbianco@cygnus.com>
Subject: gcj/59
Date: 04 Oct 1999 14:19:26 -0600
I've looked at this a bit.
jv-scan won't report any syntax errors it thinks it finds in the
source. Is this a bug? I don't know. I modified my local jv-scan to
print error messages, and I got this:
creche. jv-scan --print-main Primes.java
Primes.java: 133: parse error
This reveals a bug in parse-scan.y, which I haven't yet tracked down.
I believe it is related to the declaration of the loop variable in the
first argument to the `for'.
This method of maintaining parse-scan.y is very brittle. Is there
some other approach we could take?
Tom