Zsh Mailing List Archive
Messages sorted by: Reverse Date, Date, Thread, Author

Re: More rabbit-holes with unset variables



On Thu, Nov 26, 2020 at 4:41 PM Bart Schaefer <schaefer@xxxxxxxxxxxxxxxx> wrote:
>
> On Thu, Nov 26, 2020 at 1:21 PM Felipe Contreras
> <felipe.contreras@xxxxxxxxx> wrote:
> >
> > I asked who objected to the specific behavior I quoted.
>
> I'm not going to dig through the austin-group archives to try to
> distinguish which of the two parts of the quoted behavior (inherit, or
> otherwise not set) was the source of anyone's objection.  I concede
> that the explanatory paragraph in the rationale did not call out
> either of those behaviors.

The question was not addressed to you, but to the person that brought
up the bug report.

A quick look at the bug report doesn't show anyone objecting to that.

> > On Thu, Nov 26, 2020 at 2:42 PM Bart Schaefer <schaefer@xxxxxxxxxxxxxxxx> wrote:
> >
> > > so a the only useful "declared but not set" variable is a simple
> > > scalar.
> >
> > And by scalar I suppose you mean string.
>
> I mean the simplest form of what zsh refers to as "scalar" internally.
> Yes, that's ordinarily representable in C by "char[]", but in the
> abstract that doesn't matter.

Strings in C are typically declared as "char *", not "char []".

-- 
Felipe Contreras




Messages sorted by: Reverse Date, Date, Thread, Author