Related articles |
---|
Run-time representation of classes jon@ffconsultancy.com (Jon Harrop) (2009-01-27) |
Re: Run-time representation of classes cr88192@hotmail.com (cr88192) (2009-01-30) |
Re: Run-time representation of classes gneuner2@comcast.net (George Neuner) (2009-01-30) |
Re: Run-time representation of classes armelasselin@hotmail.com (Armel) (2009-01-30) |
Re: Run-time representation of classes ftu@fi.uu.nl (2009-01-31) |
Re: Run-time representation of classes michael@schuerig.de (Michael Schuerig) (2009-02-02) |
Re: Run-time representation of classes cr88192@hotmail.com (cr88192) (2009-02-03) |
Re: Run-time representation of classes gneuner2@comcast.net (George Neuner) (2009-02-04) |
Re: Run-time representation of classes michael@schuerig.de (Michael Schuerig) (2009-02-05) |
Re: Run-time representation of classes cr88192@hotmail.com (cr88192) (2009-02-05) |
[3 later articles] |
From: | "Armel" <armelasselin@hotmail.com> |
Newsgroups: | comp.compilers |
Date: | Fri, 30 Jan 2009 10:57:13 +0100 |
Organization: | les newsgroups par Orange |
References: | 09-01-055 09-01-063 |
Keywords: | OOP |
Posted-Date: | 01 Feb 2009 16:03:10 EST |
> adding versioning is not much more than this, namely it involves the
> addition of a table of "versions" (each version context then holding the
> various offset tables, ...). each instance then containing a version
> number
> along with the class pointer (applying a group of changes to an object
> creates a new version context, and a new version number).
It could have been built into each object in the other 'direction' also, I
mean having each instance contain a 'versioned_class' pointer, and then each
'versioned_class' having its 'version+class' information, you would win one
int per instance and one class_desc.version_array[version] indirection.
just my 2 cents
Armel
Return to the
comp.compilers page.
Search the
comp.compilers archives again.