diff options
| author | Tilghman Lesher <tilghman@meg.abyt.es> | 2009-08-10 19:49:41 +0000 |
|---|---|---|
| committer | Tilghman Lesher <tilghman@meg.abyt.es> | 2009-08-10 19:49:41 +0000 |
| commit | 4344e26b097b85ae90c90429c19aa13e01ddac13 (patch) | |
| tree | addee19ae990147ca78354e05e6febf4fe693533 /doc/CODING-GUIDELINES | |
| parent | 642bec4d6fea7afad99b6a4853418081137a48ba (diff) | |
Merged revisions 211583 via svnmerge from
https://origsvn.digium.com/svn/asterisk/branches/1.4
........
r211583 | tilghman | 2009-08-10 14:48:48 -0500 (Mon, 10 Aug 2009) | 1 line
Conversion specifiers, not format specifiers
........
git-svn-id: https://origsvn.digium.com/svn/asterisk/trunk@211584 65c4cc65-6c06-0410-ace0-fbb531ad65f3
Diffstat (limited to 'doc/CODING-GUIDELINES')
| -rw-r--r-- | doc/CODING-GUIDELINES | 7 |
1 files changed, 4 insertions, 3 deletions
diff --git a/doc/CODING-GUIDELINES b/doc/CODING-GUIDELINES index 8fb213e13..4261f2013 100644 --- a/doc/CODING-GUIDELINES +++ b/doc/CODING-GUIDELINES @@ -419,9 +419,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 ------------------ |