It seems that pharo 1.3 introduced that the image quits if an error happens during startup. What are
the reasons for this?
Or what's the state of the email below?
Andrea
Camillo Bruni schrieb:
While working on Coral we encountered a rather annoying behavior of pharo
images when starting up.
We wanted to check if we can debug the CoralScriptLoader, but of corse since this happens at image startup time this is not a good idea…
HOWEVER we were no longer able to run the image as it immediately crashes during the startup.
Now I wonder if it would make sense to add a couple of on:do: in SmalltalkImage
>> snapshot:anQuit: to collect the errors of all the startup scripts and then
only show them after all other startupListItems are processed.
All in all the behavior would not much differ from what is going on right now,
but would prevent stupid users like me from losing a whole image.
camillo
