[DGD] Upgrading clones with changed internal representation

[Noah Gibbs]

  Phantasmal doesn't currently have a good way to deal with instances or clones
on this one.  Phantasmal currently calls an "upgraded" function for each
*class*, but not for each instance of that class.  You'd have to keep your own
list right now, which would be annoying to say the least.

  You could make your own ObjectD track extra information to do this, but I
haven't put a lot of thought into how to do it efficiently...

  DGD, by default, initializes each freshly-added field (including ones that
changed type) to an appropriate "null" value, and of course deleted fields just
go away.  So you're correct that in many cases you'll want something more
interesting/complicated to happen.

--- Carter Cheng <carter_cheng at yahoo.com> wrote:

> Thanks for the responses to my previous query on the
> mailing list. Unfortunately I do have another query. I
> believe from my reading that DGD automatically
> upgrades clones of an old inheritable to a new
> inheritable if it is superceded. But how is this
> possible if the internal representation changes
> substantially or does dgd make some assumptions when
> mapping old variables in the old object state to the
> new object? 
> 
> Assuming for the moment DGD itself does not provide a
> mechanism for coping with drastic change to the
> internal representation I suspect that it's possible
> to implement on the library level. Does Phantasmal do
> this? Or is it like reflection perhaps something I
> would need to implement if I wanted it.  
> 
> Thanks in advance,
> 
> Silenus. 
> 
> 
> ___________________________________________
> https://mail.dworkin.nl/mailman/listinfo/dgd
> 





      ____________________________________________________________________________________
Park yourself in front of a world of choices in alternative vehicles. Visit the Yahoo! Auto Green Center.
http://autos.yahoo.com/green_center/