This is the mail archive of the java-patches@sources.redhat.com mailing list for the Java project.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]

Re: Patch: error->warning when assigning to final field

To: Mark Wielaard <mark at klomp dot org>
Subject: Re: Patch: error->warning when assigning to final field
From: Per Bothner <per at bothner dot com>
Date: 14 Jan 2001 14:04:29 -0800
Cc: java-patches at sources dot redhat dot com
References: <m2r926owi3.fsf@kelso.bothner.com><20010114222433.A24259@klomp.org> <m2n1ctolie.fsf@kelso.bothner.com><20010114225014.C24802@klomp.org>

Mark Wielaard <mark@klomp.org> writes:

> Ah, I see. Sorry about my confusion. You are right when talking about
> compiling from bytecode. Although I think it is strange that the JLS
> explicitly forbits it but the JVM allows it. Do you know why the JVM
> allows for this non-intuitive behaviour?

No. Quite possible an oversight in the original verifier, and they
decided not to change it.  Also, this allows an implementation to put
initialization code is put in a helper method, as I believe Gcj
sometimes does.
-- 
	--Per Bothner
per@bothner.com   http://www.bothner.com/~per/

References:
- Patch: error->warning when assigning to final field
  - From: Per Bothner
- Re: Patch: error->warning when assigning to final field
  - From: Mark Wielaard
- Re: Patch: error->warning when assigning to final field
  - From: Per Bothner
- Re: Patch: error->warning when assigning to final field
  - From: Mark Wielaard

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]