zsh-workers
 help / color / mirror / code / Atom feed
From: DervishD <zsh@dervishd.net>
To: Zsh Workers <zsh-workers@sunsite.dk>
Subject: getopts does not follow SUS
Date: Sat, 3 Sep 2005 13:17:34 +0200	[thread overview]
Message-ID: <20050903111727.GA762@DervishD> (raw)

    Hi all :)

    SUS require that getopts is 'reset' if OPTIND is assigned the
value 1, so the following is expected:

    $ getopts "-" option --ta
    $ echo -- $option
    -
    $ OPTIND=1
    $ getopts "-" option --ta
    $ echo -- $option
    -

    But zsh doesn't do that:

    $ getopts "-" option --ta
    $ echo -- $option
    -
    $ OPTIND=1
    $ getopts "-" option --ta
    zsh: bad option -t
    $ echo -- $option
    ?

    But if we assign 0 to OPTIND under zsh:

    $ getopts "-" option --ta
    $ echo -- $option
    -
    $ OPTIND=0
    $ getopts "-" option --ta
    $ echo -- $option
    -

    The same in bash (whose getopts *does* follow SUS):

    $ getopts "-" option --ta
    $ echo -- $option
    -
    $ OPTIND=1
    $ getopts "-" option --ta
    $ echo -- $option
    -

    The relevant section in SUS is:

    SUS->Shell & Utilities->Utilities->getopts

    I don't have a copy of POSIX, so I don't know if the same applies
in POSIX :?

    Unfortunately, fixing this will probably break any script that
already uses OPTIND to 'reset' getopts and assigns a value of 0,
unless '0' is kept as a back-compatibility value (SUS says that any
value other than 1 is unspecified, so...

    I've tested under version 4.2.5, Linux, PC (i686). If any other
data is needed (or tests, or whatever) just tell.

    Thanks in advance :)

    Raúl Núñez de Arenas Coronado

-- 
Linux Registered User 88736 | http://www.dervishd.net
http://www.pleyades.net & http://www.gotesdelluna.net
It's my PC and I'll cry if I want to...


                 reply	other threads:[~2005-09-03 11:13 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20050903111727.GA762@DervishD \
    --to=zsh@dervishd.net \
    --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).