Re: suspend() and resume(INT, ERR)

• Date: Wed, 5 Feb 1997 08:58:26 PST
• From:
  m.sanderson@bohm.anu.edu.au (Matthew Sanderson)
• Content-Type: text/plain; charset="us-ascii"

>it's a bug. I think it was addressed earlier. resume(E_NONE) panics the
>server...
>I think the next patch (whenever it comes around) has a fix for that..
>
>Even your own BushMOO has it archived...
>http://www.bushnet.qld.edu.au/list/moo-cow/msg.004018

The fact that resume(taskid, E_NONE) could crash the server is a separate
issue, and one that that patch apparently addresses. That bug and the patch
for it have very little to do with resume()'s behaviour when passed an ERR
apart from E_NONE in its second arg. That behaviour may (arguably) be a
design flaw/bug, but it isn't 'a bug'. It was intentionally coded this way.

So please, Erik, consider this a plea to fix the design bug too before I
write much code like " v = `suspend() ! ANY' " ...

--Matthew.

Matthew Sanderson
m.sanderson@student.anu.edu.au
The Australian National University, Canberra.

===========================================================================
"Computers in the future may weigh no more than 1.5 tons."
     --Popular Mechanics, forecasting the relentless march of science, 1949
===========================================================================

• Prev: Re: suspend() and resume(INT, ERR)
• Next: Re: suspend() and resume(INT, ERR)
• Index: MOO-cows
• Thread: MOO-cows