2011/9/22 Marcus Denker <marcus.denker@inria.fr>
Hi,

There are two changesets waiting for integrating in 1.4 that have serious consequences:

- Ephemerons. The VM level changes are in the Cog VMs build on Jenkins, but have not
�been integrated in the VMMaker codebase.

� � � �http://code.google.com/p/pharo/issues/detail?id=4265

- Finalization code checks for #hasNewFinalization
�This is true in the current VMs build in Jenkins, but in older VMs this is not in.

� � � �http://code.google.com/p/pharo/issues/detail?id=4483

There are two options:

� � � �a) integrate in
� � � �b) not integrate it

a) means that the image runs on older VMs, too.

"runs" or "will not run"?
because if it runs, it is not a problem no?



b) means we accept that we can never improve anything for real.

There will be more changes coming... e.g. imagine we have a Vector Graphics Canvas
as some point next year... what will we do? use it or not use it to stay compatible?

In any case, I am in favor to go ahead and change.
Moreover, I am not sure it is a big deal here, since it will not impact application code.
It will be probably different for the new Vector Graphics Canvas.

Luc�

� � � �Marcus


--
Marcus Denker -- http://marcusdenker.de