10 years back the VM source was in the image, this included vmmaker and an encoded zip file for all the C source files need to build the VM on the platform, aka macintosh. Out of that the vmVersion primitive would just return the update number of the image used to build the VM because they were synchronized. Today that number has little meaning, and is different on each platform, since it reflects the image used to build the VM, and says nothing about which version of vmmaker was used to make the VM. http://isqueak.org/getAttributeIntoLength On 9-Aug-09, at 10:08 AM, Damien Cassou wrote:

2009/8/9 Stéphane Ducasse <stephane.ducasse@inria.fr>:

...

So I do not know what to think. I have the latest vm and this is the one which executed the image. Of course we will have to change this vmVersion to write the exact pharo image number which is here 10413

I think that the version printed is the one that generated the VM sources. You can't change it without regenerating the VM or hacking the C source code.

-- Damien Cassou http://damiencassou.seasidehosting.st

"Lambdas are relegated to relative obscurity until Java makes them popular by not having them." James Iry

_______________________________________________ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

-- = = = ======================================================================== John M. McIntosh <johnmci@smalltalkconsulting.com> Twitter: squeaker68882 Corporate Smalltalk Consulting Ltd. http://www.smalltalkconsulting.com = = = ========================================================================