Re: [SERVER] optional verb call by server

• Date: Mon, 25 Mar 1996 19:16:17 PST
• From:
  Bill Garrett <defender@fly.net>
• cc: moo-cows@parc.xerox.com
• Content-Type: TEXT/PLAIN; charset=US-ASCII
• In-Reply-To: <12209015@prancer.Dartmouth.EDU>

> potentially undesireable "side effects".  For example move() always checks
> accept(), among other things.  One MOO that I've seen implemented the builtin
> priority_post() to move things unconditionally.  Perhaps either more
> $server_options or new, simpler builtins could be added)

For what it's worth, I wrote a trivial change to the way movement is 
handled for IdMOO.  Instead of calling WHERE:accept(WHAT) as tradition 
dictates, the builtin calls #0:accept(WHAT, WHERE), and #0:accept is 
programmed to call WHERE:accept(WHAT) normally.  I'd propose that people 
interested in de-side-effecting builtins follow that course instead of 
making an all-or-nothing server option.
Def.

• Re: [SERVER] optional verb call by server
• From: Jefferson.M.Dubrule@dartmouth.edu (Jefferson M. Dubrule)

• Prev: Re: [SERVER] optional verb call by server
• Next: Re: [SERVER] optional verb call by server
• Index: MOO-cows
• Thread: MOO-cows