Re: Too many tasks? overhead questions.

[eachus@spectre.mitre.org (Robert I. Eachus)]

In article <dewar.862310793@merv> dewar@merv.cs.nyu.edu (Robert Dewar) writes:

  > Be very careful about recommending the use of protected types. They are
  > by no means a general abstraction mechanism (the abstraction is severely
  > limited by the restriction on potentially blocking operations).

  Ah, the wonders of the English language which allows one word to
mean so many different things. ;-)  The objects in a dungeon may or
may not be objects in the programming (or OO) sense.  They are things
which can be picked up by players and NPCs (non-player characters) and
moved from place to place, but in the programming sense do not have an
associated thread of control.  Usually you just want to move them from
room to room or to the player's backpack or hand, and to display them
when the room or player is displayed.

   The only thing I could see causing the type of problem that Robert
Dewar is worried about would be a potion of sleep or some such.  But
the implementor is going to have to handle sleep right in any case.
If a player casts a sleep spell, only the target creature should be
out of commission until the spell wears off.  Of course this allows
some creativity on the part of the dungeon builder--going to sleep
from such a spell could allow you some "last wishes" before you start
to snore...



--

					Robert I. Eachus

with Standard_Disclaimer;
use  Standard_Disclaimer;
function Message (Text: in Clever_Ideas) return Better_Ideas is...