Bert,

Exactly how does this work in terms of porting?  I see relatively little in
the image for generating a platform specific build tree from which one could
generate a specific VM.  There is FFIPlugin class >>writeSupportFiles,
InterpreterSupportCode class >> writeMacSourceFiles, and the portable files
have #ifdef areas in them.

Ohshima-san ports Squeak to iPAQ, but I use a "stock" image, and there are
no iPAQ specific packages from the server that can be used to generate a
WinCE build tree for eVC.  Is it intended that as his port becomes stable,
that the WinCE code is embedded into the image?

What about plugins, resources, make files, eVC project files, etc?  You can
generalize that inquiry for all platforms: how comprehensive is it intended
that the Squeak image have all of the material necessary to generate a VM,
and when will this be realized in actuality?

	--- Noel

-----Original Message-----
From: Bert Freudenberg [mailto:bert at isg.cs.uni-magdeburg.de]
Sent: Monday, May 21, 2001 5:31
To: squeak at cs.uiuc.edu
Subject: Re: VM source in Squeak?


On Sun, 20 May 2001, Galchin Vasili wrote:

> Hello,
>
>     I downloaded Squeak source tar ball and untar'd.
> I saw many peices in C, but I couldn't find the VM
> written in Squeak. ??

The VM is implemented *in* Squeak, not in external files. The C files you
see in the src/generated directory are the result of translating the
Squeak sources to C for compilation by a regular compiler. You find the
actual implementation in the image. The core is in the classes Interpreter
and ObjectMemory, while additional stuff is in all the VMConstruction-*
class categories.

-- Bert