| TIP: Click on subject to list as thread! | ANSI |
| echo: | |
|---|---|
| to: | |
| from: | |
| date: | |
| subject: | limiting scope of acceptable command line parm |
HI Paul,
following up a message from Richard Webb to Paul Quinn:
PQ> Is that what you had in mind, mate?
RW> Maybe, but what happens to ifnumber I wonder if the bonehead that
RW> invokes it types something which is an alpha string as
RW> the command line parm? Have to try that and see what kind
RW> of choke we get.
RW> ONce I know how it chokes, I"m golden.
Yup, we figured out how it chokes. Returns errorlevel 255,
which means syntax fubar. So, if a bonehead types in a non
numeric command line parm ifnumber's going to give us some
argument about bad syntax. Can use that.
Was working on another batch project, my vessels
reconciliation file we talked about in this echo, cleaning
up the reports it generates and was testing some code I
intended to use for it, and in so doing crash tested what I
wanted to crash test for this project as well.
THe other code was critical, as it runs in automation while
I"m in bed or absent, so it's important to get right the
first time .
Regards,
Richard
--- timEd 1.10.y2k+
* Origin: Radio REscue net operations BBS (1:116/901)SEEN-BY: 10/1 11/200 331 34/999 120/228 123/500 128/2 187 140/1 222/2 226/0 SEEN-BY: 236/150 249/303 250/306 261/20 38 100 1381 1404 1406 1410 1418 SEEN-BY: 266/1413 280/1027 320/119 393/68 396/45 633/104 260 267 285 640/954 SEEN-BY: 690/682 734 712/0 313 848 800/432 801/161 189 2222/700 2320/100 105 SEEN-BY: 2320/200 5030/1256 @PATH: 116/901 3634/12 123/500 261/38 633/260 712/848 633/267 |
|
| SOURCE: echomail via fidonet.ozzmosis.com | |
Email questions or comments to sysop@ipingthereforeiam.com
All parts of this website painstakingly hand-crafted in the U.S.A.!
IPTIA BBS/MUD/Terminal/Game Server List, © 2025 IPTIA Consulting™.