Re: [PATCH] declarednull: rename DECLARED to NULL

[Daniel Shahaf <d.s@daniel.shahaf.name>]

Bart Schaefer wrote on Sun, Jan 03, 2021 at 10:26:48 -0800:
> No, that's not it.  I'm trying to find a word that describes the STATE
> of the variable, independent of its value.  It happens that the "spec"
> that we're importing from posix-ish shells means that this particular
> state is always paired with the state of "unset-ness" but regardless
> of your arguments of functional equivalence, neither of these states
> is an actual value of NULL.

Could you summarize the bits that need to be named and the corresponding shell
language incantations/semantics?

Is this anything like using «struct foo **p» in C to denote a single parameter
that has three possible states:
.
    (!p)
    (p && !*p)
    (p && *p)

> > So It seems your code and my code agree with the behavior of both A
> > and B. The only unknown is what A and B mean.
> >
> > Agreed?
> 
> Yes, although I would not say "unknown".  More like "unnamed".  Also,
> your script doesn't observe that "current zsh: B(on)" does not mean
> the same thing that "patched zsh: B(on)" means (at least for my patch
> and I think for yours).
>