Re: expression evaluation problem

From	Greg Wooledge <wooledg@eeg.ccf.org>
Newsgroups	gnu.bash.bug
Subject	Re: expression evaluation problem
Date	2019-07-25 13:34 -0400
Message-ID	<mailman.2228.1564076078.2688.bug-bash@gnu.org> (permalink)
References	(1 earlier) <20190724175103.GN1218@eeg.ccf.org> <5D38A6BF.9020309@tlinx.org> <20190724184943.GO1218@eeg.ccf.org> <5D39E6E4.8030902@tlinx.org> <20190725173408.GX1218@eeg.ccf.org>

Show all headers | View raw

On Thu, Jul 25, 2019 at 10:29:08AM -0700, L A Walsh wrote:
> On 2019/07/24 11:49, Greg Wooledge wrote:
> >               $((expression))
> >
> >        The expression is treated as if it were within  double  quotes,


> I didn't use $((...)), I'd put the whole thing in ((...)) which I hoped
> would treat the whole expression consistently.

       ((expression))
              The expression is evaluated according to the rules described be‐
              low under ARITHMETIC EVALUATION.

[...]

ARITHMETIC EVALUATION

[...]

       Shell variables are allowed as operands; parameter  expansion  is  per‐
       formed before the expression is evaluated.

Back to gnu.bash.bug | Previous | Next | Find similar | Unroll thread

Thread

Re: expression evaluation problem Greg Wooledge <wooledg@eeg.ccf.org> - 2019-07-25 13:34 -0400

csiph-web