Re: New binaries

John,
Thanks for the explanation.

Strongtalk is a bit of a halfway house between the two. All of the
code resides as compiled methods (bytecode) preserved in the image
between restarts. OTOH, most dynamic state is not preserved between
restarts. So no preservation of windows a la Squeak. Each start is a
fresh state, both for application data and for the native code cache
(though there is an experimental inlining database that can be used to
store and reload the inlining state of compiled methods).

Right now there is no easy way to bootstrap an image from scratch, nor
is there an interactive command line. You can run scripts from the
command line. These are just collections of Smalltalk fileIn chunks,
and are therefore easily editable, though clearly not ideal. In that
sense, I guess, it would not be much different to GNU Smalltalk from a
coding perspective.

Over the next months I hope to add a UI for OSX and then maybe for
Linux. If someone would like to contribute an interactive command line
capability that would be great.

talksmall

On Dec 23, 5:53=A0pm, John Cowan <[email protected]> wrote:
> In GNU Smalltalk, an image is just a binary cache of loaded source
> files: there are no bits in an image that aren't the result of loading
> source code. =A0As such, it is more like a Java .jar file than a
> traditional ST image.
>
> IIRC, there are bits in the Squeak image that result from global
> assignments done under ST-76.
>

You can follow me on twitter at http://twitter.com/smalltalkhacker

--

You received this message because you are subscribed to the Google Groups "=
Strongtalk-general" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to strongtalk-general+unsubscrib=
[email protected].
For more options, visit this group at http://groups.google.com/group/strong=
talk-general?hl=3Den.