Re: call_function() and $bf_FOO()

• Date: Sat, 27 Apr 1996 18:14:01 PDT
• From:
  Michael Brundage <anomaly@u.washington.edu>
• Cc: moo-cows@parc.xerox.com
• Content-Type: TEXT/PLAIN; charset=US-ASCII
• In-Reply-To: <Pine.LNX.3.91.960427185739.4759A-100000@darkowl.pr.mcs.net>

On Sat, 27 Apr 1996, Don Schwarz wrote:
> Oh, and while I'm at it, shouldn't the MOO panic when #0 is recycled?  Or
> maybe just make recycle() refuse to recycle it?  I don't see how the MOO
> could function at all without #0, nor do I see any reason why it should
> ever need to be recycled.  Of course recycling $player could probably do
> just as much damage, but the server doesn't directly communicate with
> $player like it does with #0.

The server should definitely not panic when #0 is recycled.  I have
recycled #0 twice, both times on purpose, and had no problems whatsoever.
If you want to prevent an object from being recycled because it is somehow
crucial to your database, then you should protect it with a wrapper in
$recycle.


anomaly@u.washington.edu

• call_function() and $bf_FOO()
• From: Don Schwarz <darkowl@darkowl.pr.mcs.net>

• Prev: Re: call_function() and $bf_FOO()
• Next: Re: call_function() and $bf_FOO()
• Index: MOO-cows
• Thread: MOO-cows