Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > gnu.bash.bug > #14316 > unrolled thread

Re: Number with sign is read as octal despite a leading 10#

Back to article view | Back to gnu.bash.bug

This discussion starts older than the indexed window; earlier articles aren't shown. The article labeled Started by below is the oldest one visible, not the original post.

Contents

  Re: Number with sign is read as octal despite a leading 10# Greg Wooledge <wooledg@eeg.ccf.org> - 2018-07-10 11:04 -0400

#14316 — Re: Number with sign is read as octal despite a leading 10#

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")

[toc] | [standalone]

Back to top | Article view | gnu.bash.bug

csiph-web