17 May
2009
17 May
'09
10:56 p.m.
+1
I always thought that MAAutoSelectorAccessor is not really usefull!
Cheers,
Gerhard
On Sun, May 17, 2009 at 10:41 PM, Lukas Renggli <renggli(a)gmail.com> wrote:
GemStone
can't migrate an object that is on the stack (as a receiver),
this means that
the normal Magritte mechanism for creating variables doesn't
work in GemStone...callers of readUsing: ... the solution for GemStone is to
flip the logic:
I don't understand the problem. As far as I understand this only
appears when the MAAutoSelectorAccessor is used. Magritte itself (with
the exception of the respective test case) and Pier does not make use
of this functionality.
Personally I never use MAAutoSelectorAccessor, I rather use the
refactoring tools. If nobody opposes I would propose to remove it?
Cheers,
Lukas
--
Lukas Renggli
http://www.lukas-renggli.ch
_______________________________________________
Magritte, Pier and Related Tools ...
https://www.iam.unibe.ch/mailman/listinfo/smallwiki