[845] in Coldmud discussion meeting

root meeting help first first in chain previous in chain previous next next in chain last in chain last

Re: inheritance

daemon@ATHENA.MIT.EDU (Thu Nov 30 16:49:59 1995 )

Date: Thu, 30 Nov 1995 17:31:06 -0500 (EST)
From: Dave Wallace <dwallace@ssnet.com>
To: Brandon Gillespie <brandon@tombstone.sunrem.com>
cc: coldstuff@tombstone.sunrem.com
In-Reply-To: <Pine.BSF.3.91.951130133127.547B-100000@tombstone.sunrem.com>

On Thu, 30 Nov 1995, Brandon Gillespie wrote:

> Encapsulation.  MOO breaks encapsulation by allowing one to inherit 
> values, which is incorrect.  Cold is simply more strict about it.  It 
> does cause problems when trying to code designes based off the MOO model, 
> but once you get used to how it works in relation to the Cold model, it 
> is actually a nice addition.

Ok, I can see that, but did you mention once that you were planing allow 
individual parameters to be marked for some such behavior? 

At any rate I can adapt :) 

This leads then to another question:
  If I specificly assign the parameter from the parent in an .init_ 
method that is called on the child at the time of @spawning:
	that_parameter = .parents()[1].get_that_value(); 

and if that_value happens to be a long list, is the whole list _copied_ or 
is a reference passed?