DLL access on Windows

[Shaping]

>> Right, but why the different behavior for little.image startup (Hi, there!) 
>> versus startup of my work.image, which returns True?  The two are the same 
>> except for the renaming.
>
> Ah. I misunderstood your question. When you save an image, it saves the entire 
> state including the call stack. When you load a saved image, you are 
> continuing where you left off.

Yes, so it is with a Smalltalk image, as well.
>
> Try the following examples:
>  [saveImageNamed: 'sayHi.image'. inform: 'Hello'.] do.
>  [saveImageNamed: 'sayHiAndQuit.image'. inform: 'Hello'. quit.] do.
>
Oh, I see.  Someone saved the original little.image with a block containing both 
the #saveImageNamed: and the #inform: sends.  The block is part of the image's 
state.


Shaping