Path: utzoo!utgpu!jarvis.csri.toronto.edu!cs.utexas.edu!tut.cis.ohio-state.edu!oboe.cis.ohio-state.edu!hansell
From: hansell@oboe.cis.ohio-state.edu (Timothy Hansell)
Newsgroups: comp.lang.smalltalk
Subject: Re: Objectworks for Smalltalk-80
Summary: Nothing important really, just a clarification
Message-ID: <77720@tut.cis.ohio-state.edu>
Date: 28 Feb 90 19:04:25 GMT
References: <5888@blake.acs.washington.edu> <80500089@p.cs.uiuc.edu> <12527@nigel.udel.EDU>
Sender: news@tut.cis.ohio-state.edu
Reply-To: Tim Hansell <hansell@cis.ohio-state.edu>
Organization: Department of Redundancy Department
Lines: 29

In article <12527@nigel.udel.EDU> new@udel.edu (Darren New) writes:
>By the way, contrary to an earlier post, Objectworks is not a C++ development
>system.  It is Smaltalk-80 Version 2.5 from ParcPlace.  Unless ParcPlace
>is using Objectworks to mean two different systems or unless somebody is
>stepping on sombody else's trademarks, Objectworks is Smalltalk, not C++.
>		 -- Darren

Actually, Objectworks is the name that ParcPlace is applying to 
the underlying environment  ( in ST-80 lingo the virtual-machine )
and they have used that environment to create a programming environment
for C++  ( which was supposed to be called Synergy ).

Thus what was Smalltalk-80 is now Objectworks for Smalltalk
and what was to have been synergy is
	Objectworks for C++

The images is built up on top of the virtual machine, and for Smalltalk
the compiler compiles st-80 into the byte-codes that the virtual machine
executes, while in C++ the compiler is a C++ compiler into byte-codes.

Given the scheme they have implemented Smalltalk in they could implement
just about any language this way ( provided it is object based )


-tim

Tim Hansell
hansell@cis.ohio-state.edu
P.O. Box 687 South Charleston, Ohio, 45268