[UPDATES] First spate of 2.7alpha

Dan Ingalls Dan.Ingalls at disney.com
Sun Oct 24 05:31:52 UTC 1999


Folks -

Herewith the first set of updates for test pilots.  In case you have forgotten, here's the incantation to enable a 2.6 release image to accept updates for 2.7alpha...

	EToySystem eToyVersion: 'Squeak2.7alpha' date: Date today.

Note that  two of these changesets will only really have an effect after you build a new VM.  Therefore we will soon put a new VM on the server.  I plan to call it 2.6d (our internal desig) because it will be backward compatible, and it fixes a lingering segment bug in 2.6 (note this is unlikely to be a problem unless you are using the very latest capability of SmartReferenceStreams together with ImageSegments).

Here are the summaries...
----------------------------------

1560morphOpenFixes-di -- Dan Ingalls -- 18 October 1999
A number of fixes so that open... opetions will work right in a morphic window in MVC.

1561extSeg-tkLQ

1562selFinder2-bf -- Bert Freudenberg -- 13 October 1999
Fixes a bug that slipped into the previous changeset. Also displays the new list format even from the lower pane (morphic only)."

1563smartUpdating-sw -- Scott Wallace -- 20 October 1999
For Morphic, makes list panes and text panes of browsers, inspectors, and other tools 'smart' in the sense that they keep themselves up to date, and react intelligently when they find that changes have happened underneath them.
Two levels of service are available -- the most obliging service continuously keeps lists and code panes up to date in all windows, both active and inactive.   Where this proves to be a performance problem, users may wish to set the #smartUpdating preference to false, in which case the service is only provided at the moment of window activation.
Enhances the stepping protocol by calling #stepAt:, with the millisecondClockValue as argument, rather than simple #step, thus allowing morphs, if they care, to do something special depending on the clock value.
The 'recent submissions' browser is particularly enhanced -- try it, in Morphic, with smartUpdating set to true, and notice how it nicely tracks all incoming code.
The mvc environment benefits somewhat from these changes as well, but only upon window activation and only in the face of code disparities, rather than also list disparities.  In due course, mvc could be made to benefit more comprehensively."

1564activeVersions-sw -- Scott Wallace -- 20 October 1999
Defines VersionBrowser as a subclass of ChangeList that specifically deals with versions.  Brings the lazy-updating methodology to Versions browsers.
For both mvc and morphic, when you use a versions browser to revert a method, the browser now reformulates itself and emerges fully up to date.
In morphic, in addition, versions browsers keep themselves up to date even when they are looking at methods that have been changed elsewhere since the versions browser was launched -- the updates catch up during stepping, or, if the 'lazyUpdating' preference is false, when the window is activated.
More buttons available in the morphic versions browser if optionalMorphicButtons is true."

1565quickFix-sw -- Scott Wallace -- 21 October 1999
One quick fix to the smartUpdating code"

1566ImageSegFixes-di -- Dan Ingalls -- 18 October 1999
Add missing code required to normalize byte order of byte-type objects after byte reversal of an entire imageSegment.
Also ensure root bits get properly set according to age of segment objects and outpointed objects when loading a segment."

1567BigContexts2-di -- Dan Ingalls -- 20 October 1999
This changeSet tweaks the VM (you must rebuild it though) so that contexts now have two sizes:  16 and 56 indexable fieds, instead of the former 32 words.  These are the only two sizes used.
It also relaxes the former limits on compilation so that many more temps and deeper call nesting can be accomodated.
This changeSet also includes a few tweaks to better close the loophole of raw context creation, and to better document how proper context creation works.
The resulting VM should be able to run old images (back thru 2.0), but an old VM could crash if running a new image after some method gets compiled that requires more than the old max context size."





More information about the Squeak-dev mailing list