Hi Jan,
I���m sorry but I will not even look at it :(
nothing personal, I respect a lot the instantiations people and their product (and I know they will do a good work).
Is just that I care a lot about Pharo being open source MIT and I do not want to pollute my code with something I might have seen elsewhere (and copyrighted elsewhere)���
But of course, I can discuss my idea here and with whoever wants :)
So, I have this idea who is very simple: keep structure offsets separately.
Today all structure has something like this:
height
"This method was automatically generated"
^handle doubleAt: 17
height: anObject
"This method was automatically generated"
handle doubleAt: 17 put: anObject
which of course does not work.
with my idea this will become like this:
height
"This method was automatically generated"
^handle doubleAt: HEIGHT_OFFSET
height: anObject
"This method was automatically generated"
handle doubleAt: HEIGHT_OFFSET put: anObject
and HEIGHT_OFFSET can be initialised per session��� or with a minimal intelligence per session with a ���architecture changed��� verification.
I think this is very easy to implement and will work��� but of course I still didn���t do anything more than think about��� we���ll see when I try to implement it :)
Esteban
Hi Esteban,
Instantiations is also busy porting their VM to 64bits. They have already created a new API for OStructures so that the offsets are re calculated based on the platform alignment rules and the VM type [1].
I know Pharo is open source and VA Smalltalk is not. But a bit of cooperation should be possible I think. Both platforms benefit if libraries are easy to port and not re-inventing this wheel saves time.
Jan.