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

Re: "getopts" bugs and bad interactions with "shift"

X-seq: zsh-workers 8761
From: Zefram <zefram@xxxxxxxx>
To: schaefer@xxxxxxxxxxxxxxxxxxxxxxx (Bart Schaefer)
Subject: Re: "getopts" bugs and bad interactions with "shift"
Date: Tue, 23 Nov 1999 20:36:06 +0000 (GMT)
Cc: zsh-workers@xxxxxxxxxxxxxx
In-reply-to: <991123180832.ZM29676@xxxxxxxxxxxxxxxxxxxxxxx> from Bart Schaefer at "Nov 23, 1999 6: 8:32 pm"
Mailing-list: contact zsh-workers-help@xxxxxxxxxxxxxx; run by ezmlm

Bart Schaefer wrote:
>Question:  Is "getopts" based on some standard or emulated behavior of
>some other shell, or is it strictly a zsh thing?

It's in POSIX.2.  My rewrite was an attempt to directly implement
the text of the standard.  (I no longer have access to the standard,
unfortunately.)  As you can tell from the code, the standard definition
is pretty unpleasant.  There are places where it's not clear what state
is stored in parameters and what is supposed to be hidden, and the text
doesn't address the issue of multiple consecutive uses of getopts at all.
I wouldn't be surprised if there are actually bugs in the standard.

-zefram

References:
- "getopts" bugs and bad interactions with "shift"
  - From: Bart Schaefer

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