On Thu, 11 Jan 2007 13:56:58 +0100, Bert Freudenberg wrote:

> Of course, that's pretty much equivalent to killing the VM,

Hhm, killing the VM is not equivalent to #processShutDownList: (which is  
sent by #snapshot:andQuit:), isn't it. But it [killing] might be the only  
exit (or alt-F4, and the like) if #snapshot:andQuit: cannot do it for any  
reason.

/Klaus

> but the changes file hint is invaluable.
>
> John, you might want to learn about managing ChangeSets with a  
> ChangeSorter, which is the traditional way to deal with source code  
> packages, and then Monticello, which is an actual version control system.
>
> - Bert -
>
> On Jan 11, 2007, at 13:33 , Klaus D. Witzel wrote:
>
>> When in emergency evaluator,
>>
>>  Smalltalk snapshot: false andQuit: true
>>
>> might do what you want. All class changes and method changes are  
>> already in the .changes file and can be recovered easily using existing  
>> tools.
>>
>> HTH.
>>
>> /Klaus
>>
>> On Thu, 11 Jan 2007 08:48:49 +0100, John Ersatznom wrote:
>>
>>> Is there something I can "evaluate" that does a "save and exit" of  
>>> class and method changes (but not the image itself)? Either to save  
>>> everything changed in the way of code, or to file out everything in a  
>>> named package?
>>>
>>> For some reason giving a morph the #none borderstyle and telling it to  
>>> openInWorld has crashed Morphic badly enough that it won't resume.  
>>> "Project newMorphic enter" and suchlike don't even get me an  
>>> uncorrupted project to file things out from before exiting.
>>>
>>> Please reply to both sender and list.
>
>
>
>
>
>