Programmatically save image, and also do it periodically
Jason Johnson
jason.johnson.081 at gmail.com
Sun Jan 13 12:25:23 UTC 2008
Yea, code is journaled for sure. I have recovered code from a crash
before. My impression was that they want this image save due to
losing application data which isn't journaled.
On Jan 10, 2008 5:48 AM, Boris Popov <boris at deepcovelabs.com> wrote:
>
>
>
> I'm not a Squeak user, but in VisualWorks if you work in chunks and publish
> your work in progress few times a day you can easily recover anything in
> between from a change set in a minute or two at most depending on complexity
> of changes. Doesn't Squeak have the same capability? Image auto save just
> smells wrong to me.
>
> Cheers!
>
> -Boris (via BlackBerry)
>
>
>
> ----- Original Message -----
> From: squeak-dev-bounces at lists.squeakfoundation.org
> <squeak-dev-bounces at lists.squeakfoundation.org>
> To: squeak-dev at lists.squeakfoundation.org
> <squeak-dev at lists.squeakfoundation.org>
> Sent: Wed Jan 09 20:44:20 2008
> Subject: Re: Programmatically save image, and also do it periodically
>
>
> "tim Rowledge" <tim at rowledge.org> wrote
>
> >> Auto-save, here I come ... :-)
> > Beware of the dangers herein. If you make some dangerous change and it
> > auto-saves ... you've now got a live image with the dangerous state and
> a
> > saved image with the dangerous state.
>
> Ah, thank you for the warning! Perhaps I will use Save as New Version, (and
> set the timer a bit longer :-)
>
> Sophie
>
>
>
>
>
>
>
>
>
More information about the Squeak-dev
mailing list
|