Path: ...!eternal-september.org!feeder3.eternal-september.org!news.eternal-september.org!eternal-september.org!.POSTED!not-for-mail From: Lawrence D'Oliveiro Newsgroups: comp.os.vms Subject: Re: Local Versus Global Command Options Date: Sat, 15 Feb 2025 21:32:22 -0000 (UTC) Organization: A noiseless patient Spider Lines: 19 Message-ID: References: <67afe79c$0$719$14726298@news.sunsite.dk> MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Injection-Date: Sat, 15 Feb 2025 22:32:22 +0100 (CET) Injection-Info: dont-email.me; posting-host="df6131520bdbbf4afb3d14a2a42a67bd"; logging-data="228222"; mail-complaints-to="abuse@eternal-september.org"; posting-account="U2FsdGVkX1/MEjUmTDHvqpcxzRuei+Vp" User-Agent: Pan/0.161 (Chasiv Yar; ) Cancel-Lock: sha1:6r/AhzlaDrJzwddhBZlaWMpiaZ0= Bytes: 1954 On Sat, 15 Feb 2025 12:22:59 -0700, Mark Berryman wrote: > So, IMHO, DCL is superior in this regard. Unfortunately, no. The fundamental problem with DEC OSes (and this includes Windows) is that the command line is passed to the program as a single string buffer. On *nix systems, it is passed as an array of strings. You should be familiar with the well-known problem of one program invoking another with a command that might include characters with special meanings to a shell. On a *nix system, there is a simple way to avoid those special meanings: the first program invokes the second program directly, without going through a shell. Nowadays, there is even a simple library call to do this . This is not so easy to do with a DEC-style command line.