I kind of agree with Steve, however, it is hard to see how this will increase the quality of source code.
Alexandre On 14 May 2009, at 19:10, Cameron Sanders wrote: > > That is not always the best policy. If you provide public accessors > for your private model elements (representation), the next thing you > know people start using them! And then your model interfaces is > constrained. > > ? or am i just talking trash ? > > > On May 14, 2009, at 12:55 PM, Steve Wirts wrote: > >> Hi Folks, >> >> Would it be inappropriate to request that an effort be made at some >> point to try to provide accessors for all instance/class instance >> variables, and try to get rid of inappropriate direct variable >> accessing where possible? >> >> The "chasing variables" function is handy but seems more cumbersome >> than just putting a halt in a setter. >> >> I know this would be a lot of work but maybe it could be automated. >> >> Just tell me to shut up and go away if I'm being a nuisance. > > Oh, and please stick around... to draw attention away from my pesky > questions. > >> >> >> Steve :) > > > -cam > > _______________________________________________ > Pharo-project mailing list > [email protected] > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. _______________________________________________ Pharo-project mailing list [email protected] http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
