MOO-cows Mailing List Archive

[Prev][Next][Index][Thread]

[bmgustav@bioinformatics.weizmann.ac.il: Re: bug in #57:@shutdown?]



------- Start of forwarded message -------
Return-Path: nop@ccs.neu.edu
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
X-NS-Transport-ID: 0800207424C500FB28B3
Date: Mon, 10 Mar 1997 02:59:12 PST
From: Gustavo Glusman <bmgustav@bioinformatics.weizmann.ac.il>
Subject: Re: bug in #57:@shutdown?
In-Reply-to: <9703100340.AA18951@oreo.aspire.cs.uah.edu>
To: MOO-cows list <MOO-Cows.parc@xerox.com>
Sender: MOO-Cows-Errors@parc.xerox.com
Precedence: bulk
Resent-From: clue-cows <nop@nop.com>
Errors-To: clue-cows <nop@nop.com>

>It seems that line 8 in #57:@shutdown

Well, #57 is $command_utils, and it doesn't define a @shutdown verb.
Blah. Of course I know you meant to say $wiz:@shutdown. Just a reminder -
not all MOO databases are based on the same LambdaCore, ok?
Not to mention that the homologous line in our $wiz:@shutdown is number 18
by now...

>    if (s = match(argstr, "^in +%([0-9]+%) +"))
>
>has a bug.  Is there any reason for the requirement of trailing
>whitespace, i.e. having to type "@shutdown in 3 " (note the trailing
>whitespace) for the command to work?  If not, line 8 should read

It is best to provide some message to be shown to the users. This
requirement for trailing blankspace probably attempts to enforce that by
making a message-less @shutdown command work differently than expected.
Right, not the best way to do it.

     ____________________________________________________________
     Gustavo Glusman              Founder/administrator of BioMOO
     Gustavo@bioinfo.weizmann.ac.il    (public PGP key available)
     http://bioinfo.weizmann.ac.il/Gustavo
        Visit BioMOO, the biologists' virtual meeting place, at
     ___________ http://bioinfo.weizmann.ac.il/BioMOO ___________
------- End of forwarded message -------


Home | Subject Index | Thread Index