> On 4 Apr 2019, at 15:04, Vitor Medina Cruz wrote:
>
> Steven:
>
> Oh! I was unaware of these methods under reflection protocol! I manage to
> make it work, and it is simply AWESOME!! :)
>
> Marcus:
>
> I wanted to intercept the store generally, with any kind of slot, kind of an
> AOP ap
Steven:
Oh! I was unaware of these methods under reflection protocol! I manage to
make it work, and it is simply AWESOME!! :)
Marcus:
I wanted to intercept the store generally, with any kind of slot, kind of
an AOP aproach. I did this:
| slotLink |
slotLink := (MetaLink new
metaObject:
> On 3 Apr 2019, at 15:57, Vitor Medina Cruz wrote:
>
> Hello,
>
> Is it possible to intercept a slot store? I tried with a before metalink into
> #write:to selector, but it don't seems to work. Should I use another selector?
>
The #write:to: method is the reflective read method that imple
Also, I do not think metalinks could work on #write:to: method from
slots, because that method is not used at runtime (I do not remember
exactly but maybe somebody knows the details...).
Le 2019-04-03 16:20, Steven Costiou a écrit :
> Hi,
>
> if you are using Pharo7, you could do either on a c
Hi,
if you are using Pharo7, you could do either on a class (affects all
instances) or on an object (affects only the target instance):
> classOrObject link: yourMetaLink toSlotNamed: #slotName option: #write
It will install the metalink on all write accesses to the slot.
Note that if you tar
Hello,
Is it possible to intercept a slot store? I tried with a before metalink
into #write:to selector, but it don't seems to work. Should I use another
selector?
I would like to experiment with ivar change notification, but I don't know
what is the better approach. I know I could install a Meta
