[Vm-dev] Why become should fail on readonly objects?
Tobias Pape
Das.Linux at gmx.de
Sun Jan 14 12:44:16 UTC 2018
> On 13.01.2018, at 23:03, Nicolas Cellier <nicolas.cellier.aka.nice at gmail.com> wrote:
>
> Hi Tobias,
> I don't mean changing the value of the binding.
> I mean Environment operations like bind:to: or undeclare:from:
> But i see it's a becomeForward: not become: so it would fall in exceptional cases described by Eliot for mutating instances...
>
Yeah, I thought that bindings (or associations then) were a device to make #become: less painful on things that tangentially touch CompiledMethods..
> 2018-01-13 21:38 GMT+01:00 Tobias Pape <Das.Linux at gmx.de>:
>
>
>> On 13.01.2018, at 21:26, Nicolas Cellier <nicolas.cellier.aka.nice at gmail.com> wrote:
>>
>> CompiledMethod directly points to these...
>
> Do they?
> <Bildschirmfoto 2018-01-13 um 21.36.33.PNG>
>
>
More information about the Vm-dev
mailing list