Hi Joseph!

The smalltalk image is portable. You can use a same image on windows, unix, or mac. I develop on mac, but when I go on holidays, I continue to work on the same image using a windows. Then, when I come back, I continue the development on mac.

I remember that once Andrew mentioned some problem with little and big endian, but I can not give more info about it...

Alexandre


On Tue, Apr 05, 2005 at 07:46:21PM -0600, Joseph Graham wrote:
> Hello,
> I was looking at implementing yet another Smalltalk inspired open source
> "embeddable" interpreter for java that uses an image file as opposed to
> emitting regular java classes.  There are several reasons for this
> decision I would be happy to discuss outside the scope of this email.  I
> know there are several implementations out there that have varying
> approaches to dealing with source code and the native platform.  
> 
> I was reading the bluebook chapters 26-30 and was wondering if it is
> better to implement an interpreter that interprets bytecode instructions
> or something that reads plain source code?  I would really like to have
> a "portable" image format.  Source code is portable but tools like
> Digitalk allow one to export repositories that not only include source
> but include the debug session.  It seems that a portable bytecode
> instruction set would be ideal.  I do not know much about other
> Smalltalk implementations but I am also wondering if there is a
> "standard" Smalltalk binary image format.
> 
> Thanks for your help
> BR_joe
> 

-- 
_,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:
Alexandre Bergel  http://www.iam.unibe.ch/~bergel
^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.