Fix a comment.

diff --git a/gettext-runtime/intl/ChangeLog b/gettext-runtime/intl/ChangeLog
index b17c0ea7f1df93c89c8c233886a828b9d6550c3f..e5154da806f80d8b8769f005436408bad5db709e 100644 (file)
--- a/gettext-runtime/intl/ChangeLog
+++ b/gettext-runtime/intl/ChangeLog
@@ -1,3 +1,8 @@
+2010-11-20  Bruno Haible  <bruno@clisp.org>
+
+       Fix a comment.
+       * vasnprintf.c (VASNPRINTF): Fix comment.
+
 2010-11-07  Bruno Haible  <bruno@clisp.org>
 
        * loadmsgcat.c (get_sysdep_segment_value): Update comment.

diff --git a/gettext-runtime/intl/vasnprintf.c b/gettext-runtime/intl/vasnprintf.c
index 55dbb27af5044f81cab6078a097f003f6069b996..87389ebadb3e61092c5521066390aa33ba614b7d 100644 (file)
--- a/gettext-runtime/intl/vasnprintf.c
+++ b/gettext-runtime/intl/vasnprintf.c
@@ -4846,8 +4846,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

diff --git a/gettext-runtime/libasprintf/ChangeLog b/gettext-runtime/libasprintf/ChangeLog
index 50f619f2c42e5af45ae05fd273ff92b5aaa5da74..d3dbb49de01d024033f5368228416755a5855dcb 100644 (file)
--- a/gettext-runtime/libasprintf/ChangeLog
+++ b/gettext-runtime/libasprintf/ChangeLog
@@ -1,3 +1,8 @@
+2010-11-20  Bruno Haible  <bruno@clisp.org>
+
+       Fix a comment.
+       * vasnprintf.c (VASNPRINTF): Fix comment.
+
 2010-11-07  Bruno Haible  <bruno@clisp.org>
 
        vasnprintf: Support I flag on glibc systems.

diff --git a/gettext-runtime/libasprintf/vasnprintf.c b/gettext-runtime/libasprintf/vasnprintf.c
index 55dbb27af5044f81cab6078a097f003f6069b996..87389ebadb3e61092c5521066390aa33ba614b7d 100644 (file)
--- a/gettext-runtime/libasprintf/vasnprintf.c
+++ b/gettext-runtime/libasprintf/vasnprintf.c
@@ -4846,8 +4846,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