[squeak-dev] Make ImageSegments import-only?

Robert Hirschfeld robert.hirschfeld at gmx.net
Fri Sep 16 15:56:46 UTC 2016


Until we have an alternative implementation, it would be nice to have full image segment support to for example revive Croquet's islands. (We did that for Squeak v4, but stopped working on it with v5...)

Best,
Robert

> On 14 Sep 2016, at 15:50, Bert Freudenberg <bert at freudenbergs.de> wrote:
> 
> Okay, I've put it in the inbox as System-bf.916.
> 
> Are we sure about removing the ability to store? I just noticed that Eliot claimed to have fixed ImageSegments in System-eem.758. OTOH if nobody intends to use them it's better to get rid of the dead code.
> 
> - Bert -
> 
> On Wed, Sep 14, 2016 at 5:48 AM, H. Hirzel <hannes.hirzel at gmail.com> wrote:
> +1
> 
> On 9/13/16, Tobias Pape <Das.Linux at gmx.de> wrote:
> > +1
> > On 13.09.2016, at 22:09, Bert Freudenberg <bert at freudenbergs.de> wrote:
> >
> >> Hi all,
> >>
> >> I think there is no current usage of image segments. Project storing has
> >> been broken for a while and that's the only current use I am aware of.
> >>
> >> What about this idea:
> >>
> >> We keep ImageSegment but remove all support for writing. It would only be
> >> used for importing old projects. It would not use the VM primitives
> >> (because they are incompatible anyways).
> >>
> >> The number of methods in ImageSegment would shrink from more than 80 to
> >> 15. My SegmentLoader has 25 methods, it replaces the VM primitive. Cog
> >> appears to be fast enough to not cause a significant slowdown in loading.
> >>
> >> With this, old projects can still be imported, but writing projects would
> >> have to use some other serialization mechanism (which we discussed
> >> before). It would remove quite a bit of unused code, making the remaining
> >> code more easily understandable.
> >>
> >> Sounds good?
> >>
> >> - Bert -
> >>
> >
> >
> >
> 
> 
> 



--
Robert Hirschfeld
hirschfeld at acm.org
www.hirschfeld.org



More information about the Squeak-dev mailing list