At 23:37 6/7/00 -0400, Joseph Shraibman <[EMAIL PROTECTED]> wrote:
>Sez who? Maybe your jre happens to run that way, but IIRC the behavior
>is undefined. If I wasn't so lazy I would look it up.
sez the JLS, section 4.5.5. Yes I have it infront of me. No it's not
there because of this thread. And yes, you should have looked it up
before posting that drivvel to the full list. any other questions?
To David's original question...
both Sun's javac (1.3 ea) and Jikes (1.11) put in two initializer
bytecodes to load in whatever value you're interested in, either
into the <clinit> block or every <init> block depending on if
it's a static field or not. I suppose you could put in an
optimization that would check every type of reference feild
initializer and if it happened to be the default for the type
then ommit the bytecode. Both compilers I checked did the same
for Object = null; vs Object; ... I'm sure such a patch would
at least be considered on jikes-dev... although we'd like to
focus on a defect take down before integrating new code....
cabbey at home dot net <*> http://members.home.net/cabbey
If at first you don't succeed, just redefine 'succeed'.
Life is a sexually transmitted, 100% lethal disease.
----------------------------------------------------------------------
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
