Re: [PATCH] declarednull: rename DECLARED to NULL

[Bart Schaefer <schaefer@xxxxxxxxxxxxxxxx>]

On Sun, Mar 28, 2021 at 5:44 PM Oliver Kiddle <opk@xxxxxxx> wrote:
>
> Bart Schaefer wrote:
> > IMO the primary remaining question is
> > whether it's acceptable to make the user-visible behavior dependent on
> > the POSIX_BUILTINS option.
>
> It seems fairly self-contained and could have it's own option. typeset
> isn't a builtin. posix compatibility options aren't really improvements
> but someone might prefer this behaviour.

(I'm reading that as "typeset isn't a POSIX builtin").  There has at
least been discussion about standardizing "local" on austin-group, and
given that "local" is an alias for typeset, this (or related) behavior
might become a POSIX compatibility thing in the future.

I'm also somewhat concerned that choosing a descriptive name for a new
option is going to spawn another argument.  TYPESET_DOES_NOT_SET ?

As mentioned long ago, it could also be an emulation-mode thing,
although that makes it a lot more difficult to access at a scripting
level.

> Was there anything else outstanding like (t) output perhaps?

I believe I have dealt properly with ${(t)var}.  I'll add something to
the doc about ${emptystr[(i)]}, because that's a weird case even
without this patch.