Henrik Johansen wrote:
The code works on both Cog and Closure VMs though, so development can continue on whatever VM you desire without a split in package versions. As Cog is able to read closure-images, but not the other way around, I imagine we will want to keep releasing official images saved by the closure VM.
IMHO, we should move to Cog as soon as possible - once any major bugs, if any, are dealt with. So, change direction: abandon 1.2 (which just started) and go for 2.0, which requires an image format change (due to Cog VM). Is there a reason to hang back - Teleplace has used Cog for about a year already?
_______________________________________________ Pharo-project mailing list [email protected] http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
