Re: The best way for @beep

• Date: Fri, 6 Sep 1996 16:54:59 PDT
• From:
  Don Schwarz <darkowl@darkowl.pr.mcs.net>
• Reply-to:
  darkowl@mcs.net
• cc: Antonio Martos <martos@las.es>, MOO-cows list <MOO-Cows.parc@xerox.com>
• Content-Type: TEXT/PLAIN; charset=US-ASCII
• In-Reply-to: <Pine.SUN.3.93.960907013601.11317D-100000@xs2.xs4all.nl>

On Sat, 7 Sep 1996 kai@xs4all.nl wrote:

> Hia,
> 
> We had a problem with people who were smart enough to just eval one of the
> verbs which did substitutions, and got an escape code back:
> 
> eval me.escape = $ansi:substitute("Blah[%red]Zoo")[5]
> => ""
> (but this was an escape...)
> 
Ack!  Never write a verb that returns a string containing non-ascii
characters.  The only verb in my ANSI system (well, in 2.1, before I fixed
it to use binary strings) that accesses the escape and beep props did a raw
notify() of the text after being called from the players' :notify, instead
of the build-in so the text still went through w/o their :notify normally.
                                                      --Dark_Owl

• Re: The best way for @beep
• From: kai@xs4all.nl

• Prev: Re: The best way for @beep
• Next: bf wrappers
• Index: MOO-cows
• Thread: MOO-cows