17 May
2009
17 May
'09
11:11 p.m.
On Sun, 2009-05-17 at 22:41 +0200, Lukas Renggli wrote:
I used it in the beginning. Than the black magic scared me to
death. Never touched it again!
I'm for removing, too!
Norbert
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?