[squeak-dev] Make ImageSegments import-only?

Bert Freudenberg bert at freudenbergs.de
Thu Sep 15 12:13:03 UTC 2016

Okay. I moved it to trunk.

With this, we should be able to load most old Etoys projects. If something
doesn't work, speak up :)

- Bert -

On Thu, Sep 15, 2016 at 3:40 AM, tim Rowledge <tim at rowledge.org> wrote:

> > On 14-09-2016, at 12:56 PM, Chris Muller <asqueaker at gmail.com> wrote:
> >
> > The original purpose of ImageSegments was to leverage the
> > garbage-collector in order to have a performant serialization
> > mechanism, is that right?
> >
> > Now with Cog/Spur, its performance is probably not as advantageous,
> > and so the relative cost of its magical implementation, code size,
> > number of serializers confusion, seems unlikely it will be used by any
> > new code.
> Given that Spur is  somewhat different memory model I doubt that using the
> original idea of the image segment is of any real advantage. And given that
> the detail of the memory model is different we’d have to do assorted
> fiddling in both directions. Seems like a bit of a loser to me. Being able
> to stop keeping compatibility code working in the vm would save some
> hassles. I say ‘just dolt'
> tim
> --
> tim Rowledge; tim at rowledge.org; http://www.rowledge.org/tim
> Brain fried; core dumped.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.squeakfoundation.org/pipermail/squeak-dev/attachments/20160915/5681bde8/attachment.htm

More information about the Squeak-dev mailing list