Weird error: opts[(r)-e]: parameter not set

Weird error: opts[(r)-e]: parameter not set

[Sebastian Gniazdowski]

Hello,
I do:
    local -a opts
    zparseopts -a opts -D ${(s::):-eLdgabsTtm}

    if [[ "${#opts[@]}" -eq 0 || ( "${#opts[@]}" -eq 1 &&
    "${opts[(r)-e]}" = "-e" ) ]]; then

and this at one user setup results in error:

functionname:12: opts[(r)-e]: parameter not set

Line number points to the if. Having set -u is capable of generating
such error, however not in this case, as there is `local -a opts`. What
else can do this?

-- 
  Sebastian Gniazdowski
  psprint@fastmail.com

Re: Weird error: opts[(r)-e]: parameter not set

[Bart Schaefer]

torch% () { setopt localoptions nounset; local -a foo; print $foo[3] }
(anon): foo[3]: parameter not set

The NO_UNSET option complains not just when the array itself is not
declared, but whenever there is a dereference of an array element
that does not exist.

Re: Weird error: opts[(r)-e]: parameter not set

[Sebastian Gniazdowski]

On Sat, Oct 29, 2016, at 10:03 AM, Bart Schaefer wrote:
> torch% () { setopt localoptions nounset; local -a foo; print $foo[3] }
> (anon): foo[3]: parameter not set
> 
> The NO_UNSET option complains not just when the array itself is not
> declared, but whenever there is a dereference of an array element
> that does not exist.

I must have done something wrong when testing this, probably had "-e" in
the test array. Thanks, with Daniel's fix, the problem should be solved.

-- 
  Sebastian Gniazdowski
  psprint@fastmail.com

Re: Weird error: opts[(r)-e]: parameter not set

[Daniel Shahaf]

Sebastian Gniazdowski wrote on Sat, Oct 29, 2016 at 07:14:38 -0700:
> functionname:12: opts[(r)-e]: parameter not set

(( ${+opts[(r)-e]} ))

avoids the error.