On 03/21/2017 02:06 AM, Norbert Hartl wrote:
Hi Dale,
Am 20.03.2017 um 19:30 schrieb Dale Henrichs <dale.henrichs@gemtalksystems.com>:
Norbert.
Are you thinking of GemStone-style class versions for Pharo?
I was thinking of something less elaborate. The GemStone implementation is not very elaborate ... the `class history` exists pretty much to provide #isKindof: sanity for "two versions of the same class". The first thing that should be possible is that two classes with different shape of the same name can co-exist in the image.That might be provided by #environment. The next step would be to have something like #migrateTo: in GemStone. Meaning that in case of a class/shape change the old instance is called with the new shape as parameter so I can intercept the process of object migration.
The #history case of GemStone would be nice of it would be modular and could be loaded. I think it can be done. But the points above need to be done first.
Norbert
Dale
On 03/19/2017 06:16 AM, Norbert Hartl wrote:
How far are we to support multiple versions of the same class in an image? Are there existing approaches?
Norbert
Von meinem iPad gesendet