From: Bart Schaefer <schaefer@brasslantern.com>
To: Zsh hackers list <zsh-workers@zsh.org>
Subject: Re: One possible answer to typeset vs. unset
Date: Wed, 2 Dec 2020 10:03:38 -0800 [thread overview]
Message-ID: <CAH+w=7ZNw_-_P24m=MO16Jxj9u+BpwQAzzJ_71pOpRJiPUdMYg@mail.gmail.com> (raw)
In-Reply-To: <X8fMgx5uY0atuMZK@zira.vinc17.org>
On Wed, Dec 2, 2020, 9:19 AM Vincent Lefevre <vincent@vinc17.net> wrote:
>
> On 2020-11-28 11:49:12 -0800, Bart Schaefer wrote:
> > The typeset -AEFHLRTZailux options are applied upon the first
> > assignment to the variable.
>
> Could you explain the following behavior?
>
> zira% ./zsh -c 'typeset -E x; echo $x; echo $((x+3)); unset x; echo $((x+3));'
>
> 3.
> 3
> zira%
>
> Why do I get "3." if the -E option isn't supposed to be applied yet?
The short answer would be "because math context is magic."
The longer answer is that $((x)) is not the same as ${x} or $(($x)),
and the quoted sentence is more a description of behavior than of
implementation.
What the branch attempts to do is create a "null" concept by combining
two flags, a new one PM_DECLARED (actually an overload of one that is
used only at shell startup) plus PM_UNSET. When a variable is
assigned, both are cleared. When a variable is unset, PM_DECLARED is
cleared and PM_UNSET is asserted if necessary. When a variable is
dereferenced in the normal ${x} way, PM_UNSET results in empty string
being returned no matter what the declared type is. With the
exception of adding PM_DECLARED, this is the way that locally scoped
variables already work.
Math context doesn't care about PM_UNSET in the same way; it grabs the
value from the union in the parameter struct, which I deliberately
left unchanged as a zero-value double. This is one reason "null" is
represented in the PM_ flags rather than in the union itself. So
$((x)) comes back 0.0 instead of empty string, and $((x+3)) works like
it always did.
prev parent reply other threads:[~2020-12-02 18:04 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-28 19:49 Bart Schaefer
2020-11-28 20:00 ` Bart Schaefer
2020-11-28 20:21 ` Bart Schaefer
2020-12-01 8:54 ` Felipe Contreras
2020-12-03 21:19 ` Bart Schaefer
2020-12-04 11:04 ` Felipe Contreras
2020-12-04 15:49 ` Bart Schaefer
2020-12-04 19:47 ` Bart Schaefer
2020-12-05 0:22 ` Bart Schaefer
2020-12-05 0:28 ` Bart Schaefer
2020-12-05 0:51 ` Bart Schaefer
2020-12-05 22:17 ` Bart Schaefer
2020-12-23 23:00 ` Felipe Contreras
2020-12-02 17:18 ` Vincent Lefevre
2020-12-02 18:03 ` Bart Schaefer [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAH+w=7ZNw_-_P24m=MO16Jxj9u+BpwQAzzJ_71pOpRJiPUdMYg@mail.gmail.com' \
--to=schaefer@brasslantern.com \
--cc=zsh-workers@zsh.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.vuxu.org/mirror/zsh/
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).