Fix a comment.

* lib/vasnprintf.c (VASNPRINTF): Fix comment.

diff --git a/ChangeLog b/ChangeLog
index 9dbc0c20e00758469569cac29ed883800a64d47a..70b9ceb2dddc99fac340b4b189b43c87487b20f5 100644 (file)
--- a/ChangeLog
+++ b/ChangeLog
@@ -1,3 +1,8 @@
+2010-11-20  Bruno Haible  <bruno@clisp.org>
+
+       Fix a comment.
+       * lib/vasnprintf.c (VASNPRINTF): Fix comment.
+
 2010-11-19  Paul Eggert  <eggert@cs.ucla.edu>
 
        ftoastr: don't assume snprintf

diff --git a/lib/vasnprintf.c b/lib/vasnprintf.c
index 87b8a55b99ed19331de92855d2615c2cb638e157..18c5e39e806efef391017aa173367c4912cf5f2e 100644 (file)
--- a/lib/vasnprintf.c
+++ b/lib/vasnprintf.c
@@ -4847,8 +4847,9 @@ VASNPRINTF (DCHAR_T *resultbuf, size_t *lengthp,
                 fbp[3] = '\0';
 # else
                 /* On glibc2 systems from glibc >= 2.3 - probably also older
-                   ones - we know that snprintf's returns value conforms to
-                   ISO C 99: the gl_SNPRINTF_DIRECTIVE_N test passes.
+                   ones - we know that snprintf's return value conforms to
+                   ISO C 99: the tests gl_SNPRINTF_RETVAL_C99 and
+                   gl_SNPRINTF_TRUNCATION_C99 pass.
                    Therefore we can avoid using %n in this situation.
                    On glibc2 systems from 2004-10-18 or newer, the use of %n
                    in format strings in writable memory may crash the program