[Vm-dev] [Pharo-project] Plan/discussion/communication around new
object format
Bert Freudenberg
bert at freudenbergs.de
Wed Jun 13 07:41:25 UTC 2012
On 2012-06-13, at 05:27, Igor Stasenko wrote:
> Another (open) question, is how to deal with immutability in presence
> of become, i.e.:
>
> mutableCopy := immutableObject shallowCopy.
> immutableObject becomeForward: mutableCopy.
>
> such kind of things making immutability useless for protecting some
> critical parts of object memory,
> like preventing modification of compiled method literals:
> yes you cannot change the immutable object, but you can replace all
> pointers to it with it's own mutable copy, which is equivalent to
> making it mutable again.
Why should the VM allow become of an immutable object?
- Bert -
More information about the Vm-dev
mailing list