Path: utzoo!censor!geac!torsqnt!jarvis.csri.toronto.edu!clyde.concordia.ca!uunet!mcsun!unido!laura!atoenne
From: atoenne@laura.UUCP (Andreas Toenne)
Newsgroups: comp.lang.smalltalk
Subject: Re: Objectworks for Smalltalk-80
Message-ID: <2024@laura.UUCP>
Date: 1 Mar 90 10:01:10 GMT
References: <5888@blake.acs.washington.edu> <80500089@p.cs.uiuc.edu> <12527@nigel.udel.EDU> <77720@tut.cis.ohio-state.edu>
Reply-To: atoenne@julien.informatik.uni-dortmund.de (Andreas Toenne)
Organization: University of Dortmund, W-Germany
Lines: 27

In article <77720@tut.cis.ohio-state.edu> Tim Hansell <hansell@cis.ohio-state.edu> writes:
>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 )


WRONG!

Objectworks for C++ contains! the AT&T C++ compiler. The Smalltalk80
part of Cynergy is used for it's superior user-interface only.
As far as I'm told, the C++ compiler (and a special debugger with
certain hooks) is used to parse, compile and run the C++ software.
Cynergy uses the parsed information to maintain the C++ sources in
handy chunks and allows for cross-referencing etc. 

Concerning Objectworks for Smalltalk80....

it runs on DEC3100 and PCS RCU too.
Additionaly the version 2.3 runs on PCS Cadmus and the Atari ST.
(A port to 2.5 is planned but not yet scheduled)


	Andreas Toenne
	atoenne@unido.uucp