Smalltalk - [VW7.2] Parcelling

Author

[VW7.2] Parcelling

Andre Schnoor

2004-04-01, 9:46 am

Is there a way to dump parcels without having to change the source pointers?
As far as I understand the source code management, it should theoretically
be possible to save a parcel without *any* side effects to the current
image, similar to "file out as".

It happened to me (for the third time already) that all my sources were gone
after a parcel "save". The most annoying thing is that there is no hint at
all that something went wrong. I kept working with the corrupted image for
hours before I saw those "*** This is decompiled code ***" comments ... too
bad, 3 megs of source are garbled now (yes, I made a snapshot after each
save).

Errors occured during the dump, which obviously caused additional
corruption. It seems to me that there is no way to dump a parcel from time
to time without getting into this source pointer mess.

Any recommendation how to save a parcel *without* side effects to the image?

Thanks in advance,
Andre

P.S: Perhaps a solution might be to provide modified source pointers
(pointing to the parcel's source file) "on-the-fly" during the save
operation, without actually modifying them in the image. This would prevent
corruption and keep the actively used sources in the change log during the
development phase. The external parcel source will only be used when the
parcel is filed into another image. IMO the parcel files and the image
should be independent from each other during development.

James A. Robertson

2004-04-02, 11:36 am

On Thu, 1 Apr 2004 15:41:57 +0200, "Andre Schnoor"
<andre.schnoor@web.de> wrote:

>Is there a way to dump parcels without having to change the source pointers?
>As far as I understand the source code management, it should theoretically
>be possible to save a parcel without *any* side effects to the current
>image, similar to "file out as".
>

Don't check the 'republish' option in the parcel save dlg

>It happened to me (for the third time already) that all my sources were gone
>after a parcel "save". The most annoying thing is that there is no hint at
>all that something went wrong. I kept working with the corrupted image for
>hours before I saw those "*** This is decompiled code ***" comments ... too
>bad, 3 megs of source are garbled now (yes, I made a snapshot after each
>save).
>
>Errors occured during the dump, which obviously caused additional
>corruption. It seems to me that there is no way to dump a parcel from time
>to time without getting into this source pointer mess.
>
>Any recommendation how to save a parcel *without* side effects to the image?
>
>Thanks in advance,
>Andre
>
>P.S: Perhaps a solution might be to provide modified source pointers
>(pointing to the parcel's source file) "on-the-fly" during the save
>operation, without actually modifying them in the image. This would prevent
>corruption and keep the actively used sources in the change log during the
>development phase. The external parcel source will only be used when the
>parcel is filed into another image. IMO the parcel files and the image
>should be independent from each other during development.
>
>

<Talk Small and Carry a Big Class Library>
James Robertson, Product Manager, Cincom Smalltalk
http://www.cincomsmalltalk.com/blog/blogView

Sponsored Links