I think this depends on who is the #vmVersion inteded for. For example, if it is for users, then I would expect to get something like Cog 1.4 Cog 2.5 I mean...who care what VMMaker/PlatformCode was used? The user may not even be aware of that.<br>
<br>Now, if it is intended for VM developers, where they need such information for a bug for example, then I think that yes, both things are important: VMMaker version and platoform code.<br><br>For me, just version of VMMaker is not enough. I'd rather put the COnfigutaionOfCog version...which has no only the VMMaker version, but also the version of all its dependencies. <br>
<br>In addition, I would put the SVN version (in case the platform code come from SVN) or GIT commit hash.<br><br>Cheers<br><br>Mariano<br><br><br><br><div class="gmail_quote">On Tue, Apr 12, 2011 at 12:53 PM, Igor Stasenko <span dir="ltr"><<a href="mailto:siguctua@gmail.com">siguctua@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;"><br>
Hello,<br>
<br>
i'd like to know what we can do to clean up the mess with Cog VM<br>
versioning, so people could identify it more easily.<br>
<br>
Currently , what<br>
<br>
Smalltalk vmVersion shows is:<br>
<br>
Smalltalk vmVersion<br>
<br>
'Croquet Closure Stack VM [StackInterpreter<br>
VMMaker-oscog-IgorStasenko.Stasenko.49] StackVM VM 4.0.0'<br>
<br>
but it doesn't says anything about which version of platform sources<br>
are used to build it.<br>
Also, a version number VM 4.0.0 makes no sense..<br>
<br>
I'd really like to see what we can do to improve it.<br>
<font color="#888888"><br>
--<br>
Best regards,<br>
Igor Stasenko AKA sig.<br>
</font></blockquote></div><br><br clear="all"><br>-- <br>Mariano<br><a href="http://marianopeck.wordpress.com" target="_blank">http://marianopeck.wordpress.com</a><br><br>