Zsh Mailing List Archive Messages sorted by: Reverse Date, Date, Thread, Author

Re: posix compliance

X-seq: zsh-workers 17341
From: Jos Backus <jos@xxxxxxxxxxx>
To: zsh-workers@xxxxxxxxxx
Subject: Re: posix compliance
Date: Thu, 20 Jun 2002 12:17:33 -0700
In-reply-to: <Pine.LNX.4.44.0206201109330.10467-100000@xxxxxxxxxxxxxxxx>
Mail-followup-to: zsh-workers@xxxxxxxxxx
Mailing-list: contact zsh-workers-help@xxxxxxxxxx; run by ezmlm
References: <20020620180526.GA65950@xxxxxxxxxxxxxxxxx> <Pine.LNX.4.44.0206201109330.10467-100000@xxxxxxxxxxxxxxxx>
Reply-to: jos@xxxxxxxxxxx

On Thu, Jun 20, 2002 at 11:13:43AM -0700, Bart Schaefer wrote:
> Assignable positional parameters are an intentional feature.  There's no
> way they can cause a problem, because a POSIX conforming shell script must
> not even attempt it.  (Even in POSIX the positional parameters can be
> replaced with the `set' builtin, so claiming that they should be read-only
> does not hold water.)

Indeed, his argument that things like these were causing them lots of problems
with zsh point to poorly written scripts in the first place. But of course
he's not going to admit that, least of all in public with the bash maintainer
standing next to him.

-- 
Jos Backus                 _/  _/_/_/        Santa Clara, CA
                          _/  _/   _/
                         _/  _/_/_/             
                    _/  _/  _/    _/
jos@xxxxxxxxxxx     _/_/   _/_/_/            require 'std/disclaimer'

Follow-Ups:
- Re: posix compliance
  - From: Dan Nelson

References:
- Re: posix compliance
  - From: Jos Backus
- Re: posix compliance
  - From: Bart Schaefer

Messages sorted by: Reverse Date, Date, Thread, Author