perhaps private accessors could go into a different category?<br><br><div class="gmail_quote">On Thu, May 14, 2009 at 1:10 PM, Cameron Sanders <span dir="ltr">&lt;<a href="mailto:camsanders01@roadrunner.com">camsanders01@roadrunner.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;"><br>
That is not always the best policy. If you provide public accessors<br>
for your private model elements (representation), the next thing you<br>
know people start using them! And then your model interfaces is<br>
constrained.<br>
<br>
? or am i just talking trash ?<br>
<div><div></div><div class="h5"><br>
<br>
On May 14, 2009, at 12:55 PM, Steve Wirts wrote:<br>
<br>
&gt; Hi Folks,<br>
&gt;<br>
&gt; Would it be inappropriate to request that an effort be made at some<br>
&gt; point to try to provide accessors for all instance/class instance<br>
&gt; variables, and try to �get rid of inappropriate direct variable<br>
&gt; accessing where possible?<br>
&gt;<br>
&gt; The &quot;chasing variables&quot; function is handy but seems more cumbersome<br>
&gt; than just putting a halt in a setter.<br>
&gt;<br>
&gt; I know this would be a lot of work but maybe it could be automated.<br>
&gt;<br>
&gt; Just tell me to shut up and go away if I&#39;m being a nuisance.<br>
<br>
</div></div>Oh, and please stick around... to draw attention away from my pesky<br>
questions.<br>
<br>
&gt;<br>
&gt;<br>
&gt; Steve :)<br>
<br>
<br>
-cam<br>
<br>
_______________________________________________<br>
Pharo-project mailing list<br>
<a href="mailto:Pharo-project@lists.gforge.inria.fr">Pharo-project@lists.gforge.inria.fr</a><br>
<a href="http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project" target="_blank">http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project</a><br>
</blockquote></div><br>