This is the mail archive of the
java@gcc.gnu.org
mailing list for the Java project.
jvm wishes and gripes
- From: Adam Megacz <gcj at lists dot megacz dot com>
- To: java at gcc dot gnu dot org
- Date: 04 Feb 2002 12:06:29 -0800
- Subject: jvm wishes and gripes
- Organization: Myself
- 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@wireless-networks.com>
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.
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?
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; }
}
Plenty of other languages (Haskell, ML) let you do stuff like
this... the code above can't violate typing rules (even if B.foo()
returned actual instances of B instead of just null).
- a