Path: utzoo!utgpu!watmath!att!bellcore!rutgers!sun-barr!cs.utexas.edu!uunet!zephyr.ens.tek.com!orca!radio_flyer!paulsc
From: paulsc@radio_flyer.WV.TEK.COM (Paul Scherf;685-2734;61-028;692-4142;orca)
Newsgroups: comp.lang.ada
Subject: Re: Objectification
Keywords: objectification, activation, passivation
Message-ID: <4152@orca.WV.TEK.COM>
Date: 8 Aug 89 16:47:09 GMT
References: <534@ajpo.sei.cmu.edu> <15991@vail.ICO.ISC.COM> <539@ajpo.sei.cmu.edu>
Sender: nobody@orca.WV.TEK.COM
Reply-To: paulsc@radio_flyer.WV.TEK.COM (Paul Scherf)
Organization: Tektronix, Inc., Wilsonville, OR
Lines: 16

In article <15991@vail.ICO.ISC.COM>, rcd@ico.ISC.COM (Dick Dunn) writes:
> eberard@ajpo.sei.cmu.edu (Edward Berard) writes about many matters and
> meta-matters roughly related to OOP and moving toward it.  All well, but
> couldn't someone come up with a better word (or perhaps I should just say
> "a word") for the concept?  "Objectification" is sufficiently ugly and
> silly-sounding (sounds like it came out of a congressional committee) to be
> an impediment to the goals.

I've read several articles mentioning "Objectification",
before I figured out what "Objectification" was.
I liked the terms "activation" (reading in an object) and "passivation"
(writing out an object, so that it may be activated at a later time),
used by Brad Cox in his book.

Paul Scherf, Tektronix, Box 1000, MS 61-028, Wilsonville, OR, USA
paulsc@orca.WV.Tek.com     503-685-2734     tektronix!orca!paulsc