"Carl Mäsak" wrote:
> ] Oh, but it gets even better: it turns out they didn't really have to
> ] sneak in through native code anyway, at least as far as the JVM is
> ] concerned, since the JVM treats final variables as always writable
> to ] the class they're defined in! There's no special case fo
Author: larry
Date: Sat May 17 14:37:37 2008
New Revision: 14542
Modified:
doc/trunk/design/syn/S05.pod
Log:
Clarifications to how tied longest tokens are handled under LTM
Modified: doc/trunk/design/syn/S05.pod
==
-
On 2008 May 17, at 4:10, Carl Mäsak wrote:
Whether we're risking the loss of important compiler optimizations by
allowing overriding of variable RO-ness is not for me to say, that's
up to the compiler writers around here. It seems to me you make it
sound worse than it really is, that optimizati
Me Here (>), Carl (>>), Me Here (>>>):
>> > What is the point of marking things readonly if you can turn it off?
>>
>> There are many possible reasons, I think.
>>
>> * The code that declares the variable readonly might not be available
>> to you (compiled to bytecode, fetched by RCP etc),
>> * or
