From b48d1b2eaee5f6fddb3bc304f87634cea51da8de Mon Sep 17 00:00:00 2001 From: Tilghman Lesher Date: Mon, 10 Aug 2009 19:51:29 +0000 Subject: [PATCH] Merged revisions 211584 via svnmerge from https://origsvn.digium.com/svn/asterisk/trunk ................ r211584 | tilghman | 2009-08-10 14:49:41 -0500 (Mon, 10 Aug 2009) | 9 lines 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/branches/1.6.1@211586 65c4cc65-6c06-0410-ace0-fbb531ad65f3 --- doc/CODING-GUIDELINES | 7 ++++--- 1 file changed, 4 insertions(+), 3 deletions(-) diff --git a/doc/CODING-GUIDELINES b/doc/CODING-GUIDELINES index 2c8ba5345d..26e78529fc 100644 --- a/doc/CODING-GUIDELINES +++ b/doc/CODING-GUIDELINES @@ -386,9 +386,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 ------------------ -- 2.47.2