Newsgroups: rec.arts.int-fiction
Path: news.duke.edu!newsgate.duke.edu!nntp-out.monmouth.com!newspeer.monmouth.com!nntp.abs.net!uunet!dca.uu.net!ash.uu.net!world!not-for-mail
From: buzzard@TheWorld.com (Sean T Barrett)
Subject: Re: [Inform] Object description
Sender: news@world.std.com (Mr Usenet Himself)
Message-ID: <GqExKn.Kov@world.std.com>
Date: Wed, 23 Jan 2002 22:38:46 GMT
References: <c424e9bf.0201221114.39c5a292@posting.google.com> <a2ms03$ufq$4@foobar.cs.jhu.edu> <a2msio$1us$6@news.panix.com> <a2n9gp$vni$2@foobar.cs.jhu.edu>
Nntp-Posting-Host: shell01.theworld.com
Organization: The World Public Access UNIX, Brookline, MA
X-Newsreader: trn 4.0-test72 (19 April 1999)
Lines: 16
Xref: news.duke.edu rec.arts.int-fiction:97727

L. Ross Raszewski <lraszewski@loyola.edu> wrote:
>Finding the
>Dalek Masterplan changes the description of the machine from
>"Doohicky" to "Universe Destroyin' Device (patent pending)", and then,
>it's often more reasonable to have the Dalek Masterplan execute
>"doohicky.description="...";" than to have the doohicky have code that
>says "if (masterplan hasnt discovered) "..."; else "...";"

Really? Ick. I wouldn't want to have the doohicky's alternate
description stored in the dalek masterplan. I'd normally implement
something like this by creating a new property function on the
device, called, say, "RevealDevice()", which reassigns the
description, and then call that. If that's just going to set
a state variable, I might do that externally.

SeanB
