[svn-commits] tilghman: trunk r211584 - in /trunk: ./ doc/CODING-GUIDELINES

[SVN commits to the Digium repositories]

Author: tilghman
Date: Mon Aug 10 14:49:41 2009
New Revision: 211584

URL: http://svn.asterisk.org/svn-view/asterisk?view=rev&rev=211584
Log:
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
........

Modified:
    trunk/   (props changed)
    trunk/doc/CODING-GUIDELINES

Propchange: trunk/
------------------------------------------------------------------------------
Binary property 'branch-1.4-merged' - no diff available.

Modified: trunk/doc/CODING-GUIDELINES
URL: http://svn.asterisk.org/svn-view/asterisk/trunk/doc/CODING-GUIDELINES?view=diff&rev=211584&r1=211583&r2=211584
==============================================================================
--- trunk/doc/CODING-GUIDELINES (original)
+++ trunk/doc/CODING-GUIDELINES Mon Aug 10 14:49:41 2009
@@ -419,9 +419,10 @@
 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
 ------------------