Why whole system dumps to image?
goran.krampe at bluefish.se
goran.krampe at bluefish.se
Wed Jul 30 00:03:57 UTC 2003
Ned Konz <ned at bike-nomad.com> wrote:
> On Tuesday 29 July 2003 02:56 pm, Jens Pall wrote:
>
> > I'm fairly new to Smalltalk and Squeak and I like what I have seen
> > so far. But there is one thing I've been wondering about and that's
> > the image file. The notion of having to dump the _whole_ system if
> > I want to keep my state seems to me just plain dumb (sorry) :). Is
> > this an artifact of piggybacking on a host OS? Some sort of
> > versioning system with branches like CVS seems more appropriate, or
> > some kind of database.
>
> Well, state includes more than source code. You can get a lot done in
> Squeak without ever writing Smalltalk.
Exactly. The image is not simply "a bunch of source files". It is a an
object space.
The thing you are asking for (selectively saving/changing parts of the
object memory) is exactly what an OODB does. And we have one - Magma.
Check it out.
regards, Göran
More information about the Squeak-dev
mailing list
|