Newsgroups: comp.lang.smalltalk
Path: cantaloupe.srv.cs.cmu.edu!rochester!cornellcs!travelers.mail.cornell.edu!news.kei.com!newshost.marcam.com!news.mathworks.com!tank.news.pipex.net!pipex!howland.reston.ans.net!torn!nott!cunews!dbuck
From: dbuck@superior.carleton.ca (Dave Buck)
Subject: Re: Smalltalk compiled?
X-Nntp-Posting-Host: superior.carleton.ca
Message-ID: <DG013J.87z@cunews.carleton.ca>
Sender: news@cunews.carleton.ca (News Administrator)
Organization: Carleton University, Ottawa, Canada
References: <145318Z05101995@anon.penet.fi>
Date: Thu, 5 Oct 1995 23:26:07 GMT
Lines: 26

In article <145318Z05101995@anon.penet.fi>,
The Unknown Ranger <an397723@anon.penet.fi> wrote:
>
>
>>Is it compiled?  Yes.  It's compiled from source to bytecodes.  The
>>difference between Smalltalk and languages like C, C++, FORTRAN, etc.
>>is that the translation to native code occurs dynamically at run-time.
>
>Does this mean that Smalltalk bytecodes are p-code?  How does PP get the 
>same image to run on different machines? The runtime interpreter that's 
>specific to each machine?

Well, it's not exactly p-code but that's the idea.  To get the same
image to run on different machines, you need an interpreter (a virtual
machine) that's specific for each machine.  The image can be moved
from one system to the other (in the case of VisualWorks) without
changes.

David Buck
dbuck@ccs.carleton.ca

_________________________________
| David K. Buck                 |
| dbuck@ccs.carleton.ca         |
| The Object People             |
|_______________________________|
