Forums before death by AOL, social media and spammers... "We can't have nice things"
|    comp.os.vms    |    DEC's VAX* line of computers & VMS.    |    264,096 messages    |
[   << oldest   |   < older   |   list   |   newer >   |   newest >>   ]
|    Message 262,386 of 264,096    |
|    =?UTF-8?Q?Arne_Vajh=C3=B8j?= to Mark Berryman    |
|    Re: Local Versus Global Command Options    |
|    15 Feb 25 15:20:40    |
      From: arne@vajhoej.dk              On 2/15/2025 2:22 PM, Mark Berryman wrote:       > On *nix, one's program can define any command syntax desired since the       > command-line parsing is done entirely within the program. The shell       > doesn't really do anything except try to expand unquoted wildcards       > (which somewhat limits the use of wildcards since the program cannot       > differentiate between a source wildcard and a destination wildcard). On       > VMS, DCL can do it either way. One can define a syntax that allows DCL       > to do the parsing as Arne has shown, or one can tell DCL to simply pass       > the command line to the program and let the program do all of the       > parsing. One advantage of the former is that if the command-line fails       > to parse, the program never even has to be activated.              A VMS program has choices:       1A) SET COMM and CLI$       1B) SET COMM/OBJ, LIB$GET_FOREIGN and CLI$       2) LIB$GET_FOREIGN and custom parsing       3) Language specific way to get individual arguments              Arne              --- SoupGate-DOS v1.05        * Origin: you cannot sedate... all the things you hate (1:229/2)    |
[   << oldest   |   < older   |   list   |   newer >   |   newest >>   ]
(c) 1994, bbs@darkrealms.ca