+1<br><br>I always thought that MAAutoSelectorAccessor is not really usefull!<br><br>Cheers,<br>Gerhard<br><br><div class="gmail_quote">On Sun, May 17, 2009 at 10:41 PM, Lukas Renggli <span dir="ltr">&lt;<a href="mailto:renggli@gmail.com">renggli@gmail.com</a>&gt;</span> wrote:<br>
<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">&gt; GemStone can&#39;t migrate an object that is on the stack (as a receiver), this means that the normal Magritte mechanism for creating variables doesn&#39;t work in GemStone...callers of readUsing: ... the solution for GemStone is to flip the logic:<br>

<br>
I don&#39;t understand the problem. As far as I understand this only<br>
appears when the MAAutoSelectorAccessor is used. Magritte itself (with<br>
the exception of the respective test case) and Pier does not make use<br>
of this functionality.<br>
<br>
Personally I never use MAAutoSelectorAccessor, I rather use the<br>
refactoring tools. If nobody opposes I would propose to remove it?<br>
<br>
Cheers,<br>
Lukas<br>
<font color="#888888"><br>
--<br>
Lukas Renggli<br>
<a href="http://www.lukas-renggli.ch" target="_blank">http://www.lukas-renggli.ch</a><br>
_______________________________________________<br>
Magritte, Pier and Related Tools ...<br>
<a href="https://www.iam.unibe.ch/mailman/listinfo/smallwiki" target="_blank">https://www.iam.unibe.ch/mailman/listinfo/smallwiki</a><br>
</font></blockquote></div><br>