This is the mail archive of the
java@gcc.gnu.org
mailing list for the Java project.
Re: PATH: check definite unassigment to final variables
- From: Tom Tromey <tromey at redhat dot com>
- To: Per Bothner <per at bothner dot com>
- Cc: gcc-patches at gcc dot gnu dot org, java at gcc dot gnu dot org
- Date: 06 Dec 2001 16:57:28 -0700
- Subject: Re: PATH: check definite unassigment to final variables
- References: <3C0C34A6.7040000@bothner.com>
- Reply-to: tromey at redhat dot com
>>>>> "Per" == Per Bothner <per@bothner.com> writes:
Per> Actually, we do violate the rules in at least one area: The extra
Per> complication dealing with loop statements discussed in the JLS.
This probably won't matter in practice, but it will show up if/when we
start running Jacks against gcj.
Per> That will uncover at least one regression: With the new algorithm
Per> libjava.compile/BlankFinal.java now fails where it didn't use
Per> to. That is because the testcase is wrong - the compiler really
Per> *should* reject the program. Tom, you checked the testcase in -
Per> I don't know what you want to do about it - change it to a
Per> "non-compile" testcase?
We can just delete it. I can do that if you'd like.
Tom