zsh-workers
 help / color / mirror / code / Atom feed
From: Bart Schaefer <schaefer@brasslantern.com>
To: Jos Backus <jos@catnook.com>
Cc: zsh-workers@sunsite.dk
Subject: Re: posix compliance
Date: Thu, 20 Jun 2002 11:13:43 -0700 (PDT)	[thread overview]
Message-ID: <Pine.LNX.4.44.0206201109330.10467-100000@ns1.sodaware.com> (raw)
In-Reply-To: <20020620180526.GA65950@lizzy.catnook.com>

On Thu, 20 Jun 2002, Jos Backus wrote:

> A quick report from UseNIX: One thing Jordan Hubbard of Apple mentioned was
> that our positional parameters ($1, $2, etc.) are assignable whereas they are
> not in bash (Chet Ramey, who was also present, confirmed this). The bash
> behavior is apparently what POSIX specifies.

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.)

> He also again complained about executable size and footprint (zsh vs.
> bash), which I think was addressed earlier

I don't have an immediate answer to that, although having looked briefly
at the bash2 web site the other day and it's possible that it now has even
more of its "builtins" as loadable modules than zsh does.


  reply	other threads:[~2002-06-20 18:13 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-06-18 22:58 Clint Adams
2002-06-20 18:05 ` Jos Backus
2002-06-20 18:13   ` Bart Schaefer [this message]
2002-06-20 19:17     ` Jos Backus
2002-06-20 21:31       ` Dan Nelson
2002-06-21  5:19   ` Borsenkow Andrej
2002-06-21 11:35   ` Oliver Kiddle
2002-06-23 17:53     ` Bart Schaefer
2002-06-20 21:19 Chet Ramey
2002-06-21  4:30 ` Jos Backus

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=Pine.LNX.4.44.0206201109330.10467-100000@ns1.sodaware.com \
    --to=schaefer@brasslantern.com \
    --cc=jos@catnook.com \
    --cc=zsh-workers@sunsite.dk \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.vuxu.org/mirror/zsh/

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).