[Pharo-dev] poor state of fuel

Max Leske maxleske at gmail.com
Wed Aug 30 08:11:20 EDT 2017


In general it doesn't matter "how much" two images differ. What is relevant
are the changes to the graph of objects that are part of a snapshot, and
that includes changes to classes that are either part of the graph or have
instances that are part of the graph.

It is possible to reshape objects upon loading (
but it is certainly not automatic (some automatic migrations are possible).

One particular problem that can pop up, if you fuel out methods, are
methods who's bytecode has changed. Fuel will then stop with an error.


On 30 August 2017 at 12:56:04, H. Hirzel (hannes.hirzel at gmail.com) wrote:

On 8/30/17, Tim Mackinnon <tim at testit.works> wrote:
> Actually in my case they are similar but not identical images.

Good to know a slightly different image still can cope with a fuel
file written by another image.

Probably the results depends on which types of objects you have written.

Not sure about the influence of changes in class definitions.


> The Lambda image is a minimal early 7.0 one - but it is beforecthe
> reworks that were announced. On top of this it has my project loaded.
> The OS X image is a fat 6.1 with the same project loaded. (So a
> I am saving the walkback context.
> Fuel warns that images need to be similar for it to map objects - so my
> scenario fits that (the same image would be easier I assume).
> Tim
> Sent from my iPhone
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.pharo.org/pipermail/pharo-dev_lists.pharo.org/attachments/20170830/00503095/attachment.html>

More information about the Pharo-dev mailing list