From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <zsh-workers-request@euclid.skiles.gatech.edu>
Received: (qmail 4970 invoked from network); 28 Jan 1997 19:19:24 -0000
Received: from euclid.skiles.gatech.edu (list@130.207.146.50)
  by coral.primenet.com.au with SMTP; 28 Jan 1997 19:19:24 -0000
Received: (from list@localhost) by euclid.skiles.gatech.edu (8.7.3/8.7.3) id OAA28795; Tue, 28 Jan 1997 14:09:08 -0500 (EST)
Resent-Date: Tue, 28 Jan 1997 14:09:08 -0500 (EST)
From: blaise@zenith.att.com
Original-From: blaise@zenith.uucp
Date: Tue, 28 Jan 1997 14:12:43 -0500
Message-Id: <9701281912.AA03250@jbond.zenith.att.com>
Original-From: blaise@zenith.att.com (Blaise Tarr(457-4233) 51E61 catwoman )
To: zsh-workers@math.gatech.edu
Subject: getopts broken in 3.0.2
Resent-Message-ID: <"YTQjO3.0.s17.Kxaxo"@euclid>
Resent-From: zsh-workers@math.gatech.edu
X-Mailing-List: <zsh-workers@math.gatech.edu> archive/latest/2835
X-Loop: zsh-workers@math.gatech.edu
Precedence: list
Resent-Sender: zsh-workers-request@math.gatech.edu

getopts seems to be broken in 3.0.2 and above (it's ok in 3.0.1)
It appears that if one of the options require a parameter, then all
the other options will now expect one too.

Consider the following script:

/tmp/aa:
--------8<------------------------------
while getopts a:b OPTION
do
    echo "OPTION is $OPTION"
done
--------8<------------------------------

sample run:

~> zsh-3.0.1 /tmp/aa -b
OPTION is b


~> zsh-3.0.2 /tmp/aa -b
/tmp/aa: argument expected after -b option [1]
OPTION is ?

-- 
Blaise Tarr
btarr@attmail.com