From: Roman Perepelitsa <roman.perepelitsa@gmail.com>
To: Ray Andrews <rayandrews@eastlink.ca>
Cc: Zsh Users <zsh-users@zsh.org>
Subject: Re: forcing float arithmetic.
Date: Wed, 24 Mar 2021 22:54:36 +0100 [thread overview]
Message-ID: <CAN=4vMq_i_FDqLbnVtZdbPEb3M58qoDdFzvf8mpQJQomtZLjHQ@mail.gmail.com> (raw)
In-Reply-To: <aa6c84af-5a8c-e52a-ccb3-6a666ca2553c@eastlink.ca>
[-- Attachment #1: Type: text/plain, Size: 948 bytes --]
On Wed, Mar 24, 2021 at 10:51 PM Ray Andrews <rayandrews@eastlink.ca> wrote:
> On 2021-03-24 10:56 a.m., Bart Schaefer wrote:
> > On Wed, Mar 24, 2021 at 10:20 AM Ray Andrews <rayandrews@eastlink.ca>
> wrote:
> >> Why are answers dumbed down like that?
> > Every subexpression is considered independently, so float conversion
> > doesn't take place until the assignment is evaluated. The type of the
> > lvalue does not propagate across every rvalue.
> >
> So it's procedural rather than deliberate/designed. It's not hard to
> cope with
> still I'd vote to correct it -- one of those things where a look ahead
> could
> sorta say that if the lvalue is float, then all subsequent arithmetic
> will be
> float. Or not worth the trouble, it's easy enough to work around.
>
The behavior of zsh in this regard is consistent with C and all languages
inspired by it (C++, Java, C# and many, many others). This is really
working as intended.
Roman.
[-- Attachment #2: Type: text/html, Size: 1408 bytes --]
next prev parent reply other threads:[~2021-03-24 21:55 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-24 17:19 Ray Andrews
2021-03-24 17:56 ` Bart Schaefer
2021-03-24 21:51 ` Ray Andrews
2021-03-24 21:54 ` Roman Perepelitsa [this message]
2021-03-24 21:59 ` Bart Schaefer
2021-03-25 1:12 ` Ray Andrews
2021-03-25 1:36 ` Daniel Shahaf
2021-03-25 1:45 ` Ray Andrews
2021-03-25 2:37 ` Bart Schaefer
2021-03-25 3:22 ` Ray Andrews
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='CAN=4vMq_i_FDqLbnVtZdbPEb3M58qoDdFzvf8mpQJQomtZLjHQ@mail.gmail.com' \
--to=roman.perepelitsa@gmail.com \
--cc=rayandrews@eastlink.ca \
--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).