If you're going to proceed in this direction, I'd like to suggest
moving to a full-fledged transaction model, ideally with
support for nested and parallel transactions.

I've done this sort of thing at the framework level
to support database interface and application development,
but it's really much better done in the VM.

-dms

Marcel Weiher wrote:

> > I agree that a good copy-on-write scheme would be a really nice
> solution.  By
> > lightening the save/restore overhead, it would allow a very simple
> > checkpoint/rollback mechanism.
>
> It would also enable Squeak as a light-weight scripting engine.
>
> Anyway, it's good to hear that this is considered a good thing by
> Squeak central, even if it's not a priority right now.  Would you be
> able to provide a little support for others implementing something
> along these lines or do you think it's hopeless?  I would certainly
> be willing to burn my Squeak-cycles on something like this while I
> wait for a pronouncement on EncodingFilters/MorphicPostscipt (and
> afterwards as well).
>
> Marcel