From: Vincent Lefevre <vincent@vinc17.org>
To: Zsh hackers list <zsh-workers@sunsite.dk>
Cc: Richard Hartmann <richih.mailinglist@gmail.com>,
Peter Stephenson <p.w.stephenson@ntlworld.com>
Subject: Re: arithmetic operator precedence
Date: Tue, 17 Jun 2008 16:33:57 +0200 [thread overview]
Message-ID: <20080617143357.GO10734@prunille.vinc17.org> (raw)
In-Reply-To: <20080617132039.GK5016@sc.homeunix.net>
On 2008-06-17 14:20:39 +0100, Stephane Chazelas wrote:
> On Tue, Jun 17, 2008 at 03:02:46PM +0200, Vincent Lefevre wrote:
> [...]
> > It is unspecified. So, the shell is right to choose how it sees it.
> >
> > > If $a contains an integer constant such as -3, then as per
> > > POSIX, $((a * 3)) should be the same as $(($a * 3)), that is
> > > $((-3 * 3)).
> >
> > No, POSIX does not say that. It happens to be the same thing here
> > just because of the properties of *, but you can't deduce anything
> > for extensions.
>
> It says $((x)) is meant to be the same as $(($x))
Yes, but not more, and only if x is a valid integer constant.
Note that recognizing negative constants is not required by POSIX;
so, they are extensions, just like "1+1".
BTW, I've just sent a mail to the Austin group about that and other
things related to arithmetic expansion.
> which I understand as any occurrance of a variable name (other than
> $-, $?, $0... obviously) in $((...)) should be the same as if the $
> was not ommited (when $x contains an integer constant).
No, POSIX doesn't say that. This sentence is a mean to define the
value of x from the contents of $x. But note that parsing has already
been done and you have something like a C expression ("The arithmetic
expression shall be processed according to the rules given in
Arithmetic Precision and Operations"); variables are just replaced
by their values, like in C. Without any extension, both interpretations
are equivalent anyway.
> That's a recent addition to the text. Only recent versions of
> ash (BSD shs) support that for instance, which is why it has
> been recommanded for a while to write it $(($x + 1)) instead of
> $((x + 1)) in POSIX scripts. And I still use x=$(($x + 1)).
But if you want to use extensions and/or more complex expressions,
you should add parentheses, e.g. x=$((($x) + 1)). This will also
work.
> > And in practice, shells don't treat $((a * 3)) and
> > $(($a * 3)) in the same way:
> >
> > vin:~> a="1 + 1"
> > vin:~> echo $((a * 3))
> > 6
> > vin:~> echo $(($a * 3))
> > 4
>
> But here, $a doesn't contain an integer constant, that's out of
> the scope of POSIX.
Not completely. The shell may recognize "1 + 1" as an integer constant
as an extension, in which case 6 would be the only valid result. Note
that negative numbers are in the same case.
Also ** is out of the scope of POSIX too.
> No, POSIX does say that $((a ** 2)) is the same as $(($a ** 2))
> because $a contains an integer constant, and that's $((-3**2)).
No (see above). You are 3 times wrong. POSIX doesn't say anything
about **, POSIX doesn't say that non-trivial expressions $((a ...))
and $(($a ...)) are equivalent (and in pratice, they aren't), POSIX
doesn't say anything about negative constants (probably a bug, but
the whole section needs to be improved anyway). Perhaps instead of
saying falsehood, you should read the standards.
--
Vincent Lefèvre <vincent@vinc17.org> - Web: <http://www.vinc17.org/>
100% accessible validated (X)HTML - Blog: <http://www.vinc17.org/blog/>
Work: CR INRIA - computer arithmetic / Arenaire project (LIP, ENS-Lyon)
next prev parent reply other threads:[~2008-06-17 14:34 UTC|newest]
Thread overview: 45+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-12 9:57 Stephane Chazelas
2008-06-12 13:12 ` Mikael Magnusson
2008-06-12 13:40 ` Peter Stephenson
2008-06-12 14:47 ` Bart Schaefer
2008-06-12 15:01 ` Stephane Chazelas
2008-06-16 8:17 ` Vincent Lefevre
2008-06-16 8:07 ` Vincent Lefevre
2008-06-16 13:42 ` Peter Stephenson
2008-06-16 13:59 ` Stephane Chazelas
2008-06-16 14:33 ` Vincent Lefevre
2008-06-17 9:19 ` Richard Hartmann
2008-06-17 9:45 ` Stephane Chazelas
2008-06-17 10:24 ` Richard Hartmann
2008-06-17 10:24 ` Richard Hartmann
2008-06-17 10:38 ` Stephane Chazelas
2008-06-17 10:43 ` Peter Stephenson
2008-06-17 11:28 ` Vincent Lefevre
2008-06-17 11:46 ` Peter Stephenson
2008-06-17 12:05 ` Vincent Lefevre
2008-06-19 9:37 ` Jun T.
2008-06-19 9:54 ` Stephane Chazelas
2008-06-19 16:00 ` Vincent Lefevre
2008-06-19 16:20 ` Stephane Chazelas
2008-06-19 17:14 ` Vincent Lefevre
2008-06-19 9:58 ` Peter Stephenson
2008-06-19 12:29 ` Richard Hartmann
2008-06-19 16:04 ` Vincent Lefevre
2008-06-19 16:10 ` Mikael Magnusson
2008-06-19 16:27 ` Stephane Chazelas
2008-06-19 17:25 ` Vincent Lefevre
2008-06-19 17:20 ` Vincent Lefevre
2008-06-17 10:45 ` Richard Hartmann
2008-06-17 11:38 ` Vincent Lefevre
2008-06-17 11:19 ` Vincent Lefevre
2008-06-17 11:57 ` Stephane Chazelas
2008-06-17 12:35 ` Vincent Lefevre
2008-06-17 12:46 ` Stephane Chazelas
2008-06-17 13:02 ` Vincent Lefevre
2008-06-17 13:20 ` Stephane Chazelas
2008-06-17 14:33 ` Vincent Lefevre [this message]
2008-06-17 14:53 ` Stephane Chazelas
2008-06-17 15:49 ` Vincent Lefevre
2008-06-17 14:35 ` Stephane Chazelas
2008-06-17 15:05 ` Vincent Lefevre
2008-06-17 10:54 ` Vincent Lefevre
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=20080617143357.GO10734@prunille.vinc17.org \
--to=vincent@vinc17.org \
--cc=p.w.stephenson@ntlworld.com \
--cc=richih.mailinglist@gmail.com \
--cc=zsh-workers@sunsite.dk \
/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).