home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
The Fred Fish Collection 1.5
/
ffcollection-1-5-1992-11.iso
/
ff_disks
/
300-399
/
ff311.lzh
/
Echo
/
echo.readme
< prev
next >
Wrap
Text File
|
1990-01-31
|
2KB
|
45 lines
ECHO George Kerber 08/28/89
This new echo command should be almost totally compatible with the AmigaDOS
echo command which this replaces. This means that you can replace your
current version of echo (AmigaDOS or ARP) with this echo and all of your
batch/script files will work okay with only a few exceptions. If you are
using the FIRST and LEN option for the AmigaDOS echo command, my echo does
not support this. In the current Amiga environment, without command line
substitution and (real) piping, I can't see any use for the FIRST and LEN
options. This shouldn't be any restriction. Also, I'll be damned if I can
figure out how to let the user enter a quote from the command line. To
print a literal quote, escape a 'q'. See the docs.
Okay, so I got carried away with options. With this echo command you can
place text anywhere on the screen with any color or attribute and any
background color. See the echo.examples script to see what can be done
with this versatility.
I never know how much error checking to do on the user entered options.
Complete error checking can help a user who is having trouble with the
program. But complete error checking makes the program larger. Should the
program ignore bad option values (like trying to move the cursor to
line 2005) or should it inform the user what the allowed values are? As an
exercise in programming, I elected to try and check for every possible error
the user could make.
One error that I don't know how to catch is a missing quote.
1> echo "see the missing quote....
My echo will think that no string was entered and simply produce a blank
line as if no string was entered at all. The AmigaDOS and ARP echo's catch
this, anyone have any ideas????
George Kerber
19756 E. Linvale Drive
Aurora, Colorado 80013
(303) 693-2890
Compuserve: 74010.2132