Re: Number with sign is read as octal despite a leading 10#
From:
Greg Wooledge
Subject:
Re: Number with sign is read as octal despite a leading 10#
Date:
Tue, 10 Jul 2018 11:04:30 -0400
User-agent:
NeoMutt/20170113 (1.7.2)
On Tue, Jul 10, 2018 at 11:00:36AM -0400, Chet Ramey wrote:
> On 7/9/18 9:24 PM, Isaac Marcos wrote:
>
> > Bash Version: 4.4
> > Patch Level: 12
> > Release Status: release
> >
> > Description:
> > A value inside an arithmetic expansion is processed as octal despite using
> > a 10# preffix.
>
> An integer constant cannot contain a `+'.
>
> >
> > Repeat-By:
> > $ echo $((10#+0034))
> > 28
>
> If anything, this is bash being too liberal in accepting constants that
> begin with `base#'. There would be a good case for rejecting the `10#'
> because it's missing the value.
It also happens with negative values. I wish the original poster had
shown that case as well.
wooledg:~$ n=-019; echo "$((10#$n))"
bash-5.0: 10#-019: value too great for base (error token is "019")