zsh-users
 help / color / mirror / code / Atom feed
From: Bart Schaefer <schaefer@brasslantern.com>
To: zsh-users@zsh.org
Subject: Re: for loop 'bad math expression'
Date: Sat, 3 Feb 2024 15:52:08 -0800	[thread overview]
Message-ID: <CAH+w=7aznm0sBRqz4=Mo4q86oMzKrg0ktSEtFBGQupiWSV7WEg@mail.gmail.com> (raw)
In-Reply-To: <0875ffd7-e3a4-4ddc-9c4b-47e2c593ea4c@eastlink.ca>

On Tue, Jan 30, 2024 at 5:44 AM Ray Andrews <rayandrews@eastlink.ca> wrote:
>
> BTW Bart, just a post mortem on that: I know there are situations where
> a plain vanilla scalar is promoted to integer

As Lawrence also suggested, I don't believe that happens.  If a
parameter is created inside a math expression it will be assigned an
appropriate numeric type, but the type of an existing scalar is not
changed.

Note "created" here includes the case where the parameter was declared
but later unset and then assigned again in math context.

Parameters may also be converted to and from arrays by assignment, and
that includes converting from an array to a numeric type when assigned
in math context.  Maybe that's what you're thinking of.

> I wonder about an automatic demotion.  The
> situation plainly had nothing to do with arithmetic

Context-awareness doesn't extend that far.  Globbing is already done
and gone by the time "for" assigns its loop variable, nothing tells
"for" where the loop values came from, and shell words on a command
line carry no type information.

> perhaps automatic 'non demotion' would be possible -- zsh might have
> robust defenses against making a mistake.

You might try setopt warn_create_global to detect cases of names "leaking".


  parent reply	other threads:[~2024-02-03 23:53 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-01-30  3:39 Ray Andrews
2024-01-30  3:46 ` Ray Andrews
2024-01-30  4:04   ` Bart Schaefer
2024-01-30  4:06     ` Bart Schaefer
2024-01-30  4:17       ` Ray Andrews
2024-01-30 13:44         ` Ray Andrews
2024-01-30 14:30           ` Lawrence Velázquez
2024-02-03 23:52           ` Bart Schaefer [this message]
2024-02-04  1:14             ` Ray Andrews
2024-02-04  2:05               ` Lawrence Velázquez
2024-02-04  4:20                 ` Bart Schaefer
2024-02-04 16:08                   ` Ray Andrews
2024-02-04 20:56                     ` Lawrence Velázquez
2024-02-04 15:51                 ` Ray Andrews
2024-02-04 20:48                   ` Lawrence Velázquez
2024-02-04 21:09                     ` Bart Schaefer
2024-02-04 21:23                       ` Bart Schaefer
2024-02-05  2:10                     ` Bart Schaefer
2024-02-05  2:43                       ` Mikael Magnusson
2024-02-05  2:50                         ` Bart Schaefer
2024-02-05 15:21                       ` Ray Andrews
2024-02-05 15:48                         ` Mark J. Reed
2024-02-04 14:43               ` Mark J. Reed
2024-02-04 16:37                 ` Ray Andrews
2024-02-04 21:09                   ` Lawrence Velázquez

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=7aznm0sBRqz4=Mo4q86oMzKrg0ktSEtFBGQupiWSV7WEg@mail.gmail.com' \
    --to=schaefer@brasslantern.com \
    --cc=zsh-users@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).