Re: Typeset with array

[Oliver Kiddle <okiddle@xxxxxxxxxxx>]

Peter wrote:
> Here's where the Cunning Plan comes in: the spcial assignment behaviour

Firstly, this looks fantastic. Much of my initial basic testing seems to
already be working.

I'll mention some of the things I tried. Just in case there's something
you hadn't thought of. Some combinations aren't especially sane but
might want an error message.

  local -a foo=one
So scope needs to be handled first and array conversion later.
Similarly: typeset -i foo=(23)

I did something like the following in _git recently. It works
  arr=( one two three )
  local $arr
There is also
  local $^arr=foo
and 
  local $^^arr=foo
The nearest in bash would be:
  declare {a,b,c}=foo
which works, but not:
  declare {a,b,c}=(one two)

Bash apparently lets you use += with declare but it seems to be
meaningless because it is not using the value from the outer scope:
  $ foo=hello
  $ function foo {
  > local foo+=bye
  > echo $foo
  > }
  $ foo
  bye
  $ echo $foo
  hello
Ksh doesn't allow it. Printing an error in this case seems best which is
what you have: typeset: not valid in this context: var+

Bash allows array element assignments:
  typeset var[4]=hello
Zsh now prints "can't create local array elements"
Including when not in a function.

That could also be extended to something like var[2,7]=(1 2)

This is perhaps jumping ahead a bit but for completion, it seems we now
get -command- context after typeset. As long as -var- context is applied
inside the actual contexts, having -command- context otherwise for
typeset would probably work fine.

It seems that it is already possible to have assignments after nocorrect
so there may already be handling for this situation by copying whatever
is done for nocorrect.

Is there a reason why noglob can't precede assignments. That could be
useful.

Oliver