No Subject

• Date: Mon, 25 Sep 1995 18:22:28 PDT
• From:
  Alex Stewart <riche@crl.com>
• In-Reply-To: <95Sep25.143350pdt.6420@silk.parc.xerox.com> from "Pavel Curtis" at Sep 25 95 2:33 pm
• Resent-Date: Mon, 25 Sep 1995 19:22:27 PDT
• Resent-From: Alex Stewart <riche@crl.com>
• Resent-Message-Id: <9509260122.AA0075@localhost>
• Resent-Subject: Re: ALPHA release of LambdaMOO server 1.7.9
• Resent-To: MOO-Cows@parc.xerox.com

> -- Added the built-in function `set_connection_option(CONN, OPTION, VALUE)',
>    for controlling various optional behaviors on the connection CONN.  The only
>    allowed values for OPTION in this release are as follows:
> 	"hold-input" -- if VALUE is true, then input received on CONN will
> 	    never be treated as a command; instead, it will remain in the queue
> 	    until retrieved by a call to read().

One question here.. does this affect suspend-detection on read() calls if a 
task associated with a "hold-input"ed queue suspends?  I.e. can I:
    set_connection_option(player, "hold-input", 1);
    suspend(0);
    set_connection_option(player, "hold-input", 0);
    ...
    x = read();

..and have it not E_PERM?  If not, could this be arranged?  It would be 
_extremely_ useful under some circumstances (in particular, in conjunction 
with the notify() changes in 1.7.9), and now that "hold-input" exists the 
primary reason for E_PERMing after suspend() (namely that input would be 
processed during the suspend, screwing up all predictability of input 
destinations) can be avoided.

-R
-------------------------------------------------------------------------------
     Alex Stewart - riche@crl.com - Richelieu @ Diversity University MOO
                         http://www.crl.com/~riche/
            "Difficult answers lead to intelligent questions."

• ALPHA release of LambdaMOO server 1.7.9
• From: Pavel Curtis <pavel@parc.xerox.com>

• Prev: No Subject
• Next: object dating
• Index: MOO-cows
• Thread: MOO-cows