Re: suspend() and read()

• Date: Thu, 9 May 1996 22:25:25 PDT
• From:
  Christopher Unkel <cunkel@us.itd.umich.edu>
• cc: moo-cows.parc@xerox.com
• Content-Type: TEXT/PLAIN; charset=US-ASCII
• In-Reply-to: <v01530500adb810620045@DialupEudora>

On Thu, 9 May 1996, Matthew Sanderson wrote:

> >From 'help read()':
> 
> `Read()' may only be called by a wizard, and,
> unless <player> is given explicitly, only in a command task that has never
> been suspended by a call to `suspend()'.  Otherwise, `E_PERM' is
> returned.
[ Illustrative demonstration snipped. ]

The help file is hopelessly out of date; at this point you'll need to 
read the programmer's manual (and run through the ChangeLog from that 
version, though in this case there are no changes.

I would quota from the changelog, but I can't.  To summarize:

As of version 1.7.6, non-wizards can read() from their own connections.

As of version 1.7.9, a read() will succeed *as long as it is from the 
last task spawned from that connection's command-line*.  You can achieve 
this by non suspending, getting lucky, or setting an appropriate 
connection-option.  Read the ChangeLog for details.

I don't think there are any relevant chagnes since 1.7.9, but I could be 
wrong.


  --Chris                           cunkel@engin.umich.edu
    ResComp Network Support Technician, Bursley Hall
    "Invisibility is in the eye of the beholder."
    Home Page: http://www-personal.engin.umich.edu/~cunkel/

• suspend() and read()
• From: m.sanderson@student.anu.edu.au (Matthew Sanderson)

• Prev: suspend() and read()
• Next: Re: suspend() and read()
• Index: MOO-cows
• Thread: MOO-cows