From: Nasir Khan <rubylearner@...>
Date: 2007-06-12T04:23:35+09:00
Subject: Re: Synchronized attr_accessor

------=_Part_119092_27034855.1181589816165
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

This begs a few questions -

- Is it true for Ruby today?
- If not then will it ever be true in future?
- Is there some text somewhere where Ruby memory model for interpreter
developers? Like Java Language spec?
- Since Ruby doesnt have a volatile keyword does it mean that all variable
access is essentially non-volatile?

Thanks
Nasir

On 6/11/07, MenTaLguY <mental@rydia.net> wrote:
>
> On Tue, 12 Jun 2007 03:45:36 +0900, MenTaLguY <mental@rydia.net> wrote:
> > For instance, when reading the instance variable @obj outside the
> > protection of the lock, it is possible that a thread could @obj being
> > non-null, but not seeing the effects of initializing the object until
> > much later!
>
> Wow, that was poor grammar on my part.  Let me try again:
>
> For instance, if reading the instance variable @obj outside the protection
> of the lock, it is possible for a thread to see that @obj is non-null long
> before the effects of the object's initialize method have become visible to
> it!
>
> -mental
>
>
>

------=_Part_119092_27034855.1181589816165--