[Vm-dev] [Pharo-project] Plan/discussion/communication around new object format

Colin Putney colin at wiresong.com
Mon Jun 11 21:46:23 UTC 2012


On Mon, Jun 11, 2012 at 2:42 PM, Chris Muller <asqueaker at gmail.com> wrote:
>
>> if you remember i said before, that i don't like immutability enforced
>> through VM contract.
>>
>> imagine two frameworks, using immutability flag for their own
>> purposes, and contending for ownership
>> of same object(s)..
>>
>> IMO, there are other , better, solutions to that but i'm not going to
>> go in details...
>
> I totally agree with you here, too.  An immutability-bit is like
> static-typing, or RDBMS RI, or "truly private" methods (to which I'm
> also opposed).  Each of those enforces some past notion about that
> object/method/whatever on the present, even until it should no longer
> be the case -- at which point you simply go into the "meta settings"
> and turn it off because it got in your way.
>
> Probably better to just avoid all that in the first place.

Ok, what if we call it a "fast write-barrier provided by the VM".
Would that change your view? Igor?

Colin


More information about the Vm-dev mailing list