17 May
2009
17 May
'09
11:13 p.m.
I think MAAutoAccessor is rarely useful, except when you want to
quickly prototype an application and generate inst-vars and accessors
automatically. After the initial prototyping phase it is hardly useful
to check for accessors and inst-vars on every read and write access.
I removed it from the latest commit. If somebody really wants this
feature, it can be easily retrieved from the history and packaged
separately.
Lukas
On Sun, May 17, 2009 at 11:04 PM, Dale Henrichs
<dale.henrichs(a)gemstone.com> wrote:
If a feature is there it will be used ... I made the
changes in response to a bug report by a user.
If you get rid of it, I can toss those changes and while I'm at it, I will audit the
other GemStone-specific changes and get back to you with the ones that are still
problematic.
Dale
----- "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
_______________________________________________
Magritte, Pier and Related Tools ...
https://www.iam.unibe.ch/mailman/listinfo/smallwiki
--
Lukas Renggli
http://www.lukas-renggli.ch