[squeak-dev] The version 3.10 does not work on Linux.

Andreas Raab ha scritto:
Heh. We could keep the current version as an "internal" version, and add
an "external" version that will stay in sync with the image version.

What do you think?

        Giovanni

We can use version strings like following format:

Squeak VM xx.yy.zz (images ver aa.bb - cc.dd)

This makes it absolutely understandable, that VM having own version ,
AND works/compatible with squeak images of given versions.

2008/6/1 Giovanni Corriga <[hidden email]>:


--
Best regards,
Igor Stasenko AKA sig.

On 1-Jun-08, at 6:12 AM, Igor Stasenko wrote:

> We can use version strings like following format:
>
> Squeak VM xx.yy.zz (images ver aa.bb - cc.dd)
>
> This makes it absolutely understandable, that VM having own version ,
> AND works/compatible with squeak images of given versions.


You couldn't actually specify the *last* version of image that the vm  
would support since you can't know that in advance.

We could however number VMs based (for example) on the revision number  
of the VMMaker  release and the SVN repository (so something like  
112-675) for development systems and then simply rename them for  
putting on the squeak.org download section when ready.
Actually, it would require an easy way to change the version number  
returned to the image for getAttributes as well, so a way of  
recompiling only the version info and relinking would be best. Perhaps  
some simply header file that has just the version number string?  
Normal make would create it with vmmaker-svn and release make would  
just do 'squeakrelease'. Or whatever. I actually used to something  
rather like that for GBH back in the 80s.

tim
--
tim Rowledge; [hidden email]; http://www.rowledge.org/tim
Half the people you know are below average.

On 31-May-08, at 11:27 PM, John M McIntosh wrote:

> At the moment I'm fully occupied with a VM rewrite, post Sophie era,  
> so I'll take hints on what the new macintosh version should be  
> called...

Oh?

Well, I'll be happy to help you figure out a name. It should be  
something appropriate to the new VM you're writing... what's new and  
cool about it compared to the old VM? What's the motivation for the  
rewrite? ;-)

Colin

> By the way, I'm using an image that I was having problems with the
> file changes. We note that the stamp of the methods are not stored in
> UTF-8, in the common cases should have no problem, but if someone puts
> extended in the sign ASCII characters are stored wrong. That what I
> discovered working with the port of Glorp, if they need a reference.

  I think that the stamp is stored in UTF-8 in 3.10 as well (at least
it does in the OLPC Etoys image).  But #getPreambleFrom:at: is looking
at the sequence backward so that it cannot decode it properly.

-- Yoshiki