Path: utzoo!utgpu!jarvis.csri.toronto.edu!clyde.concordia.ca!mcgill-vision!bloom-beacon!snorkelwacker!usc!cs.utexas.edu!uunet!parcplace!khaw
From: khaw@parcplace.com (Mike Khaw)
Newsgroups: comp.lang.smalltalk
Subject: Re: Objectworks for Smalltalk-80
Message-ID: <673@parcplace.com>
Date: 4 Mar 90 07:20:52 GMT
References: <5888@blake.acs.washington.edu> <80500089@p.cs.uiuc.edu> <12527@nigel.udel.EDU> <77720@tut.cis.ohio-state.edu>
Organization: ParcPlace Systems, Mt. View, CA
Lines: 32


Actually...

ParcPlace Systems has
	(a) Objectworks for Smalltalk-80, which used to be called
		just "Smalltalk-80".
	(b) Objectworks for C++, whose early prototypes were called
		Cynergy (a pun on "C" +(+) "synergy").

The intent of the name "Objectworks" is, among other things
	(a) to emphasize that the Smalltalk-80 product is not only a
		language, but an integrated development environment.
	(b) to assert the "family resemblance" between Objectworks
		for Smalltalk-80 and and Objectworks for C++; i.e.,
		that the latter is also an integrated development
		environment for an object-oriented programming language.
	(c) to capitalize on market interest in object-oriented
		products by including the word "object" in the products'
		names.
	(d) to make clearer to those unacquainted with Smalltalk-80
		that it is an object-oriented programming system
		(we've actually had people ask if Smalltalk was a
		data communications application).

So, as San Franciscans say "don't call it 'Frisco", ParcPlace people
say "don't call it Objectworks" - we won't know whether you mean
"... for Smalltalk-80" or "... for C++" until you've established the
context.
-- 
Mike Khaw
ParcPlace Systems, Inc., 1550 Plymouth St., Mountain View, CA 94043
Domain=khaw@parcplace.com, UUCP=...!{uunet,sun,decwrl}!parcplace!khaw