Newsgroups: rec.arts.int-fiction
Path: gmd.de!jvnc.net!yale.edu!yale!gumby!wupost!uunet!mcsun!sun4nl!dutrun!dutiws!dutiag!appelo
From: appelo@dutiag.tudelft.nl (C.J. Appelo)
Subject: Re: Naive Physics
Message-ID: <appelo.723726797@dutiag>
Sender: news@dutiws.twi.tudelft.nl (news en nntp)
Organization: Delft University of Technology
References: <3150117@hpsemc.cup.hp.com> <appelo.723476373@dutiag> <Byr28J.FCF@acsu.buffalo.edu>
Date: Mon, 7 Dec 1992 11:13:17 GMT
Lines: 32

goetz@acsu.buffalo.edu (Phil Goetz) writes:

>I think your distinction is useful, but don't call them "static"
>vs. "dynamic", because the "static" properties can change.
>Obviously position changes.  Physical state can change, e.g. a block
>of ice melts.  Size can change (e.g. a hunk of cheese which you
>cut pieces off of).

>When an object inherits the value of one of these "static" properties,
>it should only be a default inheritance, and allowed to be
>overruled or to be changed later.

>Phil

I can understand the word "static" is somewhat misleading. Whatever we
call them, it's just important to note that HAVING the property
Position or PhysicalState will NOT change. The values in it will change
of course, but not the fact that they are present. This is different from
the Edible boolean, for example. An object can become edible during the
game, which can introduce the property Taste, with values like sweet, salt
etcetera. So, Position is static (changeable but not removable) and Taste
is dynamic (changeable and removable).

Jurgen.

===================================================================
| Jurgen Appelo                  |                                |
| Delft University of Technology |   When Technology Is Master,   |
| The Netherlands                |   You Reach Disaster Faster.   |
| appelo@dutiag.twi.tudelft.nl   |                                |
===================================================================

