On Wed, Jul 20, 2011 at 1:35 PM, Cédric Martínez Campos
wrote:
> Configuration Information [Automatically generated, do not change]:
> Machine: x86_64
> OS: linux-gnu
> Compiler: gcc
> Compilation CFLAGS: -DPROGRAM='bash' -DCONF_HOSTTYPE='x86_64'
> -DCONF_OSTYPE='linux-gnu' -DCONF_MACHTYPE='x86_6
Hi Cédric,
Cédric Martínez Campos wrote:
> $ echo $((08+1))
> bash: 08: too big element for the base (the error element is "08")
> [translated from spanish]
Strings of digits starting with a '0' in an arithmetic expansion are
octal numbers. The bash FAQ[*] has some details.
Hope th
Configuration Information [Automatically generated, do not change]:
Machine: x86_64
OS: linux-gnu
Compiler: gcc
Compilation CFLAGS: -DPROGRAM='bash' -DCONF_HOSTTYPE='x86_64'
-DCONF_OSTYPE='linux-gnu' -DCONF_MACHTYPE='x86_64-pc-linux-gnu'
-DCONF_VENDOR='pc' -DLOCALEDIR='/usr/share/locale' -DPACKAGE
Configuration Information [Automatically generated, do not change]:
Machine: i386
OS: freebsd8.1
Compiler: cc
Compilation CFLAGS: -DPROGRAM='bash' -DCONF_HOSTTYPE='i386'
-DCONF_OSTYPE='freebsd8.1' -DCONF_MACHTYPE='i386-portbld-freebsd8.1'
-DCONF_VENDOR='portbld' -DLOCALEDIR='/usr/local/share/loc
Chet Ramey wrote:
> I wrote the entire test suite except for the one file from Glen Fowler.
> It is (or should be) copyright GPL3 just like the rest of the distribution.
Just wanted to say thanks for the clear and quick responses. They helped.
Jonathan
Hi Eric,
> > $ printf '%-9223372036854775808s.\n' foo
> > foo.
> > $
>
> Coreutils' printf shares this misfortune. Sadly, it might even be a
> bug in the underlying glibc printf(), although I haven't tried to
> write a test program to check that, yet.
OK, well for %b and %q bash'
[adding coreutils]
On 07/20/2011 07:34 AM, Ralph Corderoy wrote:
BTW, the code for the built-in printf has a bug. For negative
field-widths it negates a negative integer without checking it will fit.
E.g. on this 64-bit machine
$ printf '%-9223372036854775808s.\n' foo
foo.
$
C
Hi Bob,
> Ralph Corderoy wrote:
> > ... But a regular file ./foo on disk does look different and it
> > still seems odd that
> > printf '\n\n\n\n\n\n\n\n\n\n\n\n' >foo
> > does a dozen one-byte write(2)s.
>
> But the only reason you know that there is a long string of newlines
> is that your