<HEAD><TITLE>discuss@charon: [1241] in "Coldmud discussion meeting"</TITLE>
<H1>[1241] in Coldmud discussion meeting</H1></HEAD>
<A HREF="/"><IMG SRC="/i-d.gif" ALT="root"></A>
<A HREF="?1241"><IMG SRC="/i-back.gif" ALT="meeting"></A>
<A HREF="/help.html"><IMG SRC="/i-help.gif" ALT="help"></A>
<A HREF="1"><IMG SRC="/i-first.gif" ALT="first"></A>
<A HREF="1235"><IMG SRC="/i-fref.gif" ALT="first in chain"></A>
<A HREF="1240"><IMG SRC="/i-pref.gif" ALT="previous in chain"></A>
<A HREF="1240"><IMG SRC="/i-prev.gif" ALT="previous"></A>
<A HREF="1242"><IMG SRC="/i-next.gif" ALT="next"></A>
<IMG SRC="/n-nref.gif" ALT="">
<IMG SRC="/n-lref.gif" ALT="">
<A HREF="1641"><IMG SRC="/i-last.gif" ALT="last"></A>
<HR><H2>Re: [COLD] public/private/protected object variables</H2>
<H3>daemon@ATHENA.MIT.EDU (Sun Mar  2 16:34:24 1997
)</H3>
<PRE>
Date: Sun, 02 Mar 1997 13:29:32 -0800
To: "Jeff T. Polczynski" &lt;jefftp@purdue.edu&gt;, "COLD" &lt;coldstuff@cold.org&gt;
From: Jeff Kesselman &lt;jeffk@tenetwork.com&gt;

At 05:18 PM 3/1/97 -0500, Jeff T. Polczynski wrote:
&gt;&gt;On Sat, 1 Mar 1997, Jeff Kesselman wrote:
&gt;&gt;&gt; I guess I'ld have to say I think its a bad ideas. I think its dilutes the
&gt;&gt;&gt; strengths of COldC-- oen of which is that it breaks your sloppy C++ habits
&gt;&gt;&gt; and FORCES yo uto learn how to write really good object orinted code.
&gt;&gt;But this isn't breaking the encapsulation--it is simply changing the
&gt;&gt;default value when a specific instance is not defined.  The variable still
&gt;
&gt;[...]
&gt;
&gt;&gt;instance in the ancestor tree)--and only change what you care about.
&gt;
&gt;This sounds like MOO's standard operation for decendants. Which I've 
&gt;really missed in ColdX. Variables default to the value defined above them 
&gt;in the public instance... I think the private, protected and public words 
&gt;sound strange when used in this respect, but I would find these features 
&gt;make more commonsense than the current system where you need to define 
&gt;values over and over again, which is bad programming in my mind.

Its handy.
What I do is inherit init routiens that do the same thing at obejct init,
so I dont feel strongly abotu it, now thatI understand it.

JK

&gt;
&gt;

</PRE>
