This is the mail archive of the
java@gcc.gnu.org
mailing list for the Java project.
Re: jvm wishes and gripes
- From: Cedric Berger <cedric at wireless-networks dot com>
- To: Adam Megacz <gcj at lists dot megacz dot com>
- Cc: java at gcc dot gnu dot org
- Date: Mon, 04 Feb 2002 21:46:25 +0100
- Subject: Re: jvm wishes and gripes
- References: <1012842846.637.9.camel@jaques> <87ofj54045.fsf@tf1.tapsellferrier.co.uk> <1012843643.1451.12.camel@jaques> <87it9d3zbe.fsf@tf1.tapsellferrier.co.uk> <1012847493.1450.14.camel@jaques> <87g04h3vzj.fsf@tf1.tapsellferrier.co.uk> <3C5EDC21.2050305 <86u1sxnha2.fsf_-_@megacz.com>
Adam Megacz wrote:
>Cedric Berger <cedric@wireless-networks.com> writes:
>
>>No. they didn't add new bytecodes (at least not in classfiles, what
>>the VM do internally is another issue).
>>
>
>If Sun ever gets up the gumption to add instructions, I dearly hope
>that stack-allocated objects and *real* generic types (not the
>expensive jdk1.4 casting syntax-sugar) are among them.
>
You mean 1.5, right?
>While I'm wishing, some cleaner syntax for closures would be nice
>too... and peace on earth... and a winnebago...
>
>I can't really be the only person who wants this stuff, can I?
>
I believe it's too late to change java bytecode. For example, what would
you do with all the microcontrollers that interprets the java bytecode
directly?
>Oh yeah, one more thing... why doesn't the Java Language spec allow
>this:
>
> class A {
> A foo() { return null; }
> }
>
> class B extends A {
> B foo() { return null; }
> }
>
Look a bit more closely at the "expensive jdk 1.4^c^c^c 1.5 casting
syntax sugar".
your code above will be valid under the new specs.
Cedric