[Vm-dev] confirm that messageSelector needs less coddling

[Eliot Miranda]

Hi All,
    "coddling" is an English term meaning to treat in an over-protective
way, so one may for example coddle a baby.
In primitivePerform and primitivePerformAt some care is taken to save
messageSelector and restore it if either
primitive fails during lookup.  Failure occurs when the number of arguments
in the perform does not match the
found method, but this is by the way.  As far as I can see saving and
restoring messageSelector is unnecessary
because it cannot be read after failure.  This is in contrast to newMethod
which is read on failure when the failing
perform method is activated.

I wanted to confirm with you in case I've missed something.  I think I'm
right even if the perform is wrapped inside
any number of other performs or executeMethods, but more heads are better
than one.

best
Eliot
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.squeakfoundation.org/pipermail/vm-dev/attachments/20090512/914b7411/attachment.htm