Hi All, On Tue, Jun 22, 2010 at 8:09 AM, Henrik Johansen < [email protected]> wrote:
> > On Jun 22, 2010, at 4:58 36PM, Yanni Chiu wrote: > > > 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? > > > - Platform availability (64bit is not supported, iPhone/iPad VM's can't run > them) > - Still buggy (I've reported 2 so far) > - No process established yet how / if to synch with current VMMaker (which > contains quite a lot of fixes not found in Cog) > - Plugin availability (f.ex. I tried building FT2Plugin using Cog structure > on OSX, and failed miserably) > - No good reason to release a backwards-incompatible image by default, when > Cog translates them by default, but not the other way around. > I just want to endorse Henry's caution. Clearly Cog is not ready to replace the existing VMs. But do note that the Stack VM is included and that should be a portable VM. I know that John McIntosh is looking at the Stack VM for iPhone. The Stack VM is not a JIT and so is cross-platform; but it does use the same context-to-stack mapping scheme as the Cog VM. What I hope will happen is that the Stack VM will replace the standard VM pretty soon, and that, because the Stack VM and the Cog VM can read each other's images that once the VM maintainers have integrated the Stack VM into the VM sources then images will move forward to the Cog format. But for the present Henry is absolutely right. best Eliot > Cheers, > Henry > _______________________________________________ > Pharo-project mailing list > [email protected] > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >
_______________________________________________ Pharo-project mailing list [email protected] http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
