Path: utzoo!attcan!uunet!van-bc!
From: lphillips@lpami.wimsey.bc.ca (Larry Phillips)
Newsgroups: comp.sys.amiga
Subject: Re: CLI-Execute bug
Keywords: cli execute bug
Message-ID: <2190@lpami.wimsey.bc.ca>
Date: 4 Nov 90 19:53:44 GMT
Lines: 42
Return-Path: <lpami!lphillips>
To: van-bc!rnews

In <phil.657695687@adam.adelaide.edu.au>, phil@adam.adelaide.edu.au (Phil Kernick) writes:
>I found the following bug in the CLI execute command:
>> copy * fubar
>execute test
>^\
>> copy * test
>echo "<"
>^\
>> execute test
><
>> execute fubar
>EXECUTE: No K directive
>execute failed returncode 20
>>
>
>The bug occurs if an execute script containing a '<' anywhere in it
>(including inside quotes as above, or inside a comment) is called up
>from another execute script.  A simple workaround this is to include
>the line:
>.bra ~
>at the top of the offending script (in fact any character can be used
>in the .bra directive, but then must not occur in the script).
>
>Has this bug been fixed in 2.0 (this is using 1.3.2)?
>
>Phil.

Gee, I hope they haven't 'fixed' a perfectly good feature.

_Some_ character has to delimit an argument. Having an argument delimitershow
up in text, how would you treat it, if you were the execute program?

-larry

--
It is not possible to both understand and appreciate Intel CPUs.
    -D.Wolfskill
+-----------------------------------------------------------------------+ 
|   //   Larry Phillips                                                 |
| \X/    lphillips@lpami.wimsey.bc.ca -or- uunet!van-bc!lpami!lphillips |
|        COMPUSERVE: 76703,4322  -or-  76703.4322@compuserve.com        |
+-----------------------------------------------------------------------+