[Info-vax] Command Line Versus Command Line

[Arne Vajhøj]

On 5/23/2024 6:32 PM, Craig A. Berry wrote:
> On 5/23/24 2:05 PM, Arne Vajhøj wrote:
>> On 5/23/2024 12:16 AM, Lawrence D'Oliveiro wrote:
>>> VMS really wants you to use a DCL-style syntax for your command 
>>> lines. It
>>> does weird things like uppercasing text in the command buffer, except 
>>> for
>>> parts in quotes, which are left as-is, but then the quotes are also left
>>> in place, so command-line parsers have to worry about dealing with text
>>> that might or might not be quoted.
>>
>> That is an oversimplified view on a complex issue.
>>
>> real: ABC def "GIH" "jkl"
>> parse=traditional:
>> CLI : ABC DEF GIH jkl
>> FC  : ABC DEF "GIH" "jkl"
>> Mix : ABC DEF GIH jkl
>> C   : abc def GIH jkl
>> DCL : ABC DEF GIH jkl
>> parse=extended:
>> CLI : ABC DEF GIH jkl
>> FC  : ABC def "GIH" "jkl"
>> Mix : ABC DEF GIH jkl
>> C   : ABC def GIH jkl
>> DCL : ABC DEF GIH jkl

> Good summary.  Did you have DECC$ARGV_PARSE_STYLE defined for the C 
> example?

Looks that way:

$ sh log *pars*

(LNM$PROCESS_TABLE)

   "DECC$ARGV_PARSE_STYLE" = "enable"

Note that I have not set it explicit - something
has set it for me.

A little investigation reveals that it is Java:

$ sear disk0:[sys0.syscommon.openjdk$80.com]java$setup.com decc
$ define'defopt' decc$fd_locking true
$ define'defopt' decc$efs_case_preserve enable  ! Enable ODS-5 names
$ define'defopt' decc$readdir_dropdotnotype enable
$ define'defopt' decc$efs_charset enable
$ define'defopt' decc$argv_parse_style enable

Arne