Path: ...!eternal-september.org!feeder3.eternal-september.org!news.eternal-september.org!eternal-september.org!.POSTED!not-for-mail
From: Mark Berryman <mark@theberrymans.com>
Newsgroups: comp.os.vms
Subject: Re: Local Versus Global Command Options
Date: Mon, 17 Feb 2025 19:23:07 -0700
Organization: A noiseless patient Spider
Lines: 73
Message-ID: <vp0qua$1dbh3$1@dont-email.me>
References: <volt3s$33lo1$1@dont-email.me> <vonh1j$3fukn$1@dont-email.me>
 <vonr8r$3ghb6$1@dont-email.me> <voo40m$3jej5$1@dont-email.me>
 <vookpo$3mk0q$1@dont-email.me> <67afe79c$0$719$14726298@news.sunsite.dk>
 <voqpjj$5mpo$1@dont-email.me> <vor156$6uru$2@dont-email.me>
 <votq85$ptnb$1@dont-email.me> <vou0nm$qq2u$2@dont-email.me>
 <vp015a$19ajm$1@dont-email.me> <vp0atu$1asp1$5@dont-email.me>
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 8bit
Injection-Date: Tue, 18 Feb 2025 03:23:07 +0100 (CET)
Injection-Info: dont-email.me; posting-host="6538c71a468d85eade026927ea31c136";
	logging-data="1486371"; mail-complaints-to="abuse@eternal-september.org";	posting-account="U2FsdGVkX19DgpnpWGRBWO3Jko7RNFtfmwfAMcK6zck="
User-Agent: Mozilla Thunderbird
Cancel-Lock: sha1:inxpQC2rglvBouzraMSkbp2T2Yw=
In-Reply-To: <vp0atu$1asp1$5@dont-email.me>
Content-Language: en-US
Bytes: 3644

On 2/17/25 2:49 PM, Lawrence D'Oliveiro wrote:
> On Mon, 17 Feb 2025 12:02:37 -0700, Mark Berryman wrote:
> 
>> On 2/16/25 5:43 PM, Lawrence D'Oliveiro wrote:
>>
>>> Consider what happens: if you pass unquoted text to program X, DCL
>>> converts it to uppercase, and I think also normalizes multiple spaces
>>> to a single space. If you don’t want the text to be uppercased or
>>> space- normalized, you put it in pairs of double quotes. But then these
>>> double quotes also get passed as part of the command line. So the
>>> receiving program has to do some non-trivial parsing just to get simple
>>> literal text via the command line.
>>
>> So, so, so very wrong.  You are *way* behind the times.
>>
>> I *never* have to quote arguments when using programs that still use
>> *nix syntax on VMS.  My arguments' case is never changed.
> 
> Prove it. It seems to me what you are claiming would break backward
> compatibility with the way VMS used to work.
> 
>> $ gs -q -P- -dNOPAUSE -dBATCH -sDEVICE=pdfwrite -sstdout=%stderr
>> -sOutputFile=<something>.pdf <something>.ps

I'm pretty sure this just did.

And no, no breakage.  Each user on each VMS system can choose how they 
want to things to work.  I could easily set things up to work the way 
you think they should work but that would be so '90s; pretty much what 
the poster from VAX/VMS showed.  I prefer to operate in the 21st century 
and take advantage of what VMS offers today, something of which you have 
proven yourself completely ignorant.

 > .
 > .
> .
> Can you show us a simple C program that just prints out its command
> arguments, and how it responds to some sample command lines?

Easily.

$ type proof.c
#include <stdio.h>

int main(int argc, char *argv[])
{
     for (int i=1; i<argc; i++)
         printf("%s\n", argv[i]);
}


$ mcr []proof These Are The Arguments
These
Are
The
Arguments

$ mcr []proof These Are The "Arguments"
These
Are
The
Arguments


Now, please crawl back into your hole.  Trolls don't do well in sunlight 
and your extreme ... obtuseness ... is showing.

Everyone else: Yes, I've once again been forced to face the fact that 
you can't fix stupid.  I won't be responding anymore.

Mark Berryman