[UPDATES] 57 for Squeak3.7alpha

Bruce O'Neel edoneel at sdf.lonestar.org
Fri Mar 5 09:16:56 UTC 2004


I noticed that too.


cheers

bruce


On Fri, Mar 05, 2004 at 12:27:16AM -0500, Doug Way wrote:
> 
> On Wednesday, March 3, 2004, at 02:16 PM, Ned Konz wrote:
> 
> >On Tuesday 02 March 2004 11:55 pm, goran.krampe at bluefish.se wrote:
> >>>Hmm, maybe.  This happens for me too, although the changeset looks 
> >>>okay
> >>>in the changesorter.  I haven't looked into why this happens.  Any
> >>>idea, Ned?
> >>
> >>Yep, look in the postscript, last line:
> >>Project spawnNewProcessAndTerminateOld: true.
> >>
> >>Same trick I used in my SM bootStrap - it essentially kills the 
> >>running
> >>Process. Possibly because Ned don't want the code running that is 
> >>filing
> >>in the .cs to return - because it would possibly be running old 
> >>Obsolete
> >>code etc.
> >>
> >>So short answer is - it is intentional. :)
> >
> >Right. I have to make a new Hand for the World after this, or things 
> >break.
> 
> It looks like this will cause a minor glitch when additional updates 
> are added to the update stream.  I added an extra update in the test 
> (internal) update stream, and if you load updates, you'll get a "Sorry 
> that name is already used" prompt because it's trying to reload 
> 5764GenieRemoval-nk again.  It's probably trying to load this one again 
> because it never was properly marked as being loaded the first time, 
> since the process was terminated.
> 
> (Actually, you can see it happen just by reloading updates in a regular 
> 5764 image.)
> 
> It's not a huge problem in this case, it just brings up the prompt and 
> then skips trying to reload that update.
> 
> Still, we might not want to do this sort of thing in the update stream 
> in the future.  Maybe there are other ways to achieve a similar 
> effect...
> 
> - Doug
> 
> 
> 

-- 
edoneel at sdf.lonestar.org
SDF Public Access UNIX System - http://sdf.lonestar.org



More information about the Squeak-dev mailing list