[DGD] Clonables versus Inheritables

[Noah Gibbs]

--- Josh Dady <jpd at indecisive.com> wrote:
> Well, strictly speaking, you can't upgrade something that is only  
> inherited either.  :)

  Heh.  True.  You have to destruct-and-recompile.

> The kernel's rules prevent multiple compiled  
> versions of the same object from existing at the same time.

  This isn't entirely true.  DGD's rules (not specifically the kernel's) keep
multiple compiled versions of the same object from existing at the same time,
unless N-1 of those versions (called issues of the object) are destructed.

> Any  
> inherited object can't be upgraded, so the master must be destroyed  
> and re-created.

  You mean the *parent* must be destroyed and re-created.  Sorry to be picky,
but "master" actually means the object from which a *clone* is created, so this
is an important distinction in this case.

  Though if an object is both cloned from and inherited from, then it's both a
master and a parent.  Anyway.

  But yes, he's correct.  To upgrade a master object (one with clones) you have
to recompile it, and to upgrade a parent object, you have to destruct the old
version and recompile the children with the new version.  These upgrade methods
are incompatible, so to fully recreate everything, all parent classes are
abstract parent classes (in the C++ or OO language sense of that word).





		
____________________________________________________
Start your day with Yahoo! - make it your home page 
http://www.yahoo.com/r/hs