[DGD] Clonables versus Inheritables

[Noah Gibbs]

  Necessary for runtime compilation, actually.  Or at least, for full upgrade.

  DGD has a restriction that you basically can't upgrade a class that is both
cloned (like, has clones of it) and inherited from.  The DGD Kernel Library
handles this by preventing you from ever making a clone or an instance of
anything with "/lib/" in the path, thus rendering it inheritable but
non-instantiable and non-clonable.

--- Stephen Miller <naubol at gmail.com> wrote:

> I've read a lot of documentation and some things still seem somewhat
> obscure to me...  Like why would someone wish to create a distinction
> between inheritable classes and clonable classes?  Is it considered
> good design for DGD?  I'm not sure what benefits would be gained.
> 
> Also, does preventing inheritance of clonable objects aid persistence
> or runtime recompiling?
> 
> N
> 
> __________________________________________
> http://mail.dworkin.nl/mailman/listinfo/dgd
> 




__________________________________________________
Do You Yahoo!?
Tired of spam?  Yahoo! Mail has the best spam protection around 
http://mail.yahoo.com