[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
printf(1) bug?
|
From: |
Eric Blake |
|
Subject: |
printf(1) bug? |
|
Date: |
Mon, 28 May 2007 16:16:00 -0600 |
|
User-agent: |
Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.0.10) Gecko/20070221 Thunderbird/1.5.0.10 Mnenhy/0.7.5.666 |
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
POSIX does not specify what should happen with:
$ /bin/printf %hhu/ 254 255 256
However, since coreutils accepts hh as an extension, should it issue a
warning if the string being printed does not fit in an unsigned char? Or
should it silently wrap around, and print 0 instead of 256? Or are we
okay with keeping status quo that the size specifiers must be valid
according to printf(3) rules, but are otherwise ignored?
- --
Don't work too hard, make some time for fun as well!
Eric Blake address@hidden
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (Cygwin)
Comment: Public key at home.comcast.net/~ericblake/eblake.gpg
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iD8DBQFGW1Sf84KuGfSFAYARAiqwAJ4qEm6YcmN9NDxGt7nRpspqLIFwNwCgivGo
BpqBZKhMuSB08X3djFAlhfE=
=E84r
-----END PGP SIGNATURE-----
- printf(1) bug?,
Eric Blake <=