aboutsummaryrefslogtreecommitdiffstats
path: root/doc
diff options
context:
space:
mode:
authortilghman <tilghman@f38db490-d61c-443f-a65b-d21fe96a405b>2009-08-10 19:48:48 +0000
committertilghman <tilghman@f38db490-d61c-443f-a65b-d21fe96a405b>2009-08-10 19:48:48 +0000
commit2a91bdfba98299c7c89b8ed8ba9b2cbabc07a07d (patch)
tree52b1a80a4d05961f80debae5534a018bb852a5be /doc
parent8cae492343324ae845b8b19d78b253d824eac10f (diff)
Conversion specifiers, not format specifiers
git-svn-id: http://svn.digium.com/svn/asterisk/branches/1.4@211583 f38db490-d61c-443f-a65b-d21fe96a405b
Diffstat (limited to 'doc')
-rw-r--r--doc/CODING-GUIDELINES7
1 files changed, 4 insertions, 3 deletions
diff --git a/doc/CODING-GUIDELINES b/doc/CODING-GUIDELINES
index 1eb4c88a0..67837e928 100644
--- a/doc/CODING-GUIDELINES
+++ b/doc/CODING-GUIDELINES
@@ -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
errors. Always check the return value of sscanf to verify that your numeric
variables successfully scanned before using them. Also, to avoid a potential
-libc bug, always specify a maximum width for each format specifier, including
-integers and floats. A good length for both integers and floats is 30, as
-this is more than generous, even if you're using doubles or long integers.
+libc bug, always specify a maximum width for each conversion specifier,
+including integers and floats. A good length for both integers and floats is
+30, as this is more than generous, even if you're using doubles or long
+integers.
* Use of functions
------------------