transactional saving of images
Hi, I have had a few occasions where I broke an image because I either ran out of disk space or had an endless loop that grew my image endlessly (I think). But why does Pharo not save the image & .changes file in hidden files named eg ~Pharo.image while it saves? Then it can rename them when saving was successful. Many unix programs do this. (I'm using pharo 6.1 so don't know if newer versions do this) -- Siemen
On 15 Nov 2019, at 11:15, Siemen Baader <siemenbaader@gmail.com> wrote:
Hi,
I have had a few occasions where I broke an image because I either ran out of disk space or had an endless loop that grew my image endlessly (I think).
But why does Pharo not save the image & .changes file in hidden files named eg ~Pharo.image while it saves? Then it can rename them when saving was successful. Many unix programs do this.
(I'm using pharo 6.1 so don't know if newer versions do this)
Hi, I think this sounds like a good idea. Marcus
Agree, sounds like a good idea. As far as I know newer versions do not do this. On Mon, Nov 18, 2019, 07:17 Marcus Denker <marcus.denker@inria.fr> wrote:
On 15 Nov 2019, at 11:15, Siemen Baader <siemenbaader@gmail.com> wrote:
Hi,
I have had a few occasions where I broke an image because I either ran out of disk space or had an endless loop that grew my image endlessly (I think).
But why does Pharo not save the image & .changes file in hidden files named eg ~Pharo.image while it saves? Then it can rename them when saving was successful. Many unix programs do this.
(I'm using pharo 6.1 so don't know if newer versions do this)
Hi,
I think this sounds like a good idea.
Marcus
participants (3)
-
Julián Maestri -
Marcus Denker -
Siemen Baader