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

Re: posix compliance

In the last episode (Jun 20), Jos Backus said:
> 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.

The only reason I can think of to disallow non-POSIX-sanctioned
behvaiour is to prevent the rampant use of such features, as has
already happened in the Linux "sh == bash" world.  You could even make
the case that zsh in sh emulation mode should allow only what POSIX
says it can do and nothing more.

If we're talking about zsh mode, then I lean the other way and say zsh
can do whatever it wants, as long as what POSIX mandates it does a
certain way, it does.

	Dan Nelson

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