Conversion specifiers, not format specifiers

git-svn-id: https://origsvn.digium.com/svn/asterisk/branches/1.4@211583 65c4cc65-6c06-0410-ace0-fbb531ad65f3
This commit is contained in:
Tilghman Lesher
2009-08-10 19:48:48 +00:00
parent 63cc189747
commit 90f3605f6f

View File

@@ -291,9 +291,10 @@ When converting from strings to integers or floats, use the sscanf function
in preference to the atoi and atof family of functions, as sscanf detects in preference to the atoi and atof family of functions, as sscanf detects
errors. Always check the return value of sscanf to verify that your numeric errors. Always check the return value of sscanf to verify that your numeric
variables successfully scanned before using them. Also, to avoid a potential variables successfully scanned before using them. Also, to avoid a potential
libc bug, always specify a maximum width for each format specifier, including libc bug, always specify a maximum width for each conversion specifier,
integers and floats. A good length for both integers and floats is 30, as including integers and floats. A good length for both integers and floats is
this is more than generous, even if you're using doubles or long integers. 30, as this is more than generous, even if you're using doubles or long
integers.
* Use of functions * Use of functions
------------------ ------------------