* ansidecl.h: Update comments reflecting previous change.

From-SVN: r45275

diff --git a/include/ChangeLog b/include/ChangeLog
index 23ba4fb7983d775760c82019553c53edbceeb66f..81d2cc2c7b591f271060482cccf5868f2094c94a 100644 (file)
--- a/include/ChangeLog
+++ b/include/ChangeLog
@@ -1,3 +1,7 @@
+2001-08-29  Kaveh R. Ghazi  <ghazi@caip.rutgers.edu>
+
+       * ansidecl.h: Update comments reflecting previous change.
+
 2001-08-27  Kaveh R. Ghazi  <ghazi@caip.rutgers.edu>
 
        * ansidecl.h (VA_OPEN, VA_CLOSE): Allow multiple uses.

diff --git a/include/ansidecl.h b/include/ansidecl.h
index 4c63fa66e4984112a9aa8db22e7f043d11335205..9a7c5777ff2ece9641045ce4a6b6b90e93b3b3c7 100644 (file)
--- a/include/ansidecl.h
+++ b/include/ansidecl.h
@@ -93,11 +93,13 @@ Foundation, Inc., 59 Temple Place - Suite 330, Boston, MA 02111-1307, USA.  */
 
 
    You can declare variables either before or after the VA_OPEN,
-   VA_FIXEDARG sequence.  You can _not_ put statements before VA_OPEN.
-   Also, VA_OPEN and VA_CLOSE are the beginning and end of a block.
-   They must appear at the same nesting level, and any variables
-   declared after VA_OPEN go out of scope at VA_CLOSE.  Unfortunately,
-   with a K+R compiler, that includes the argument list.
+   VA_FIXEDARG sequence.  Also, VA_OPEN and VA_CLOSE are the beginning
+   and end of a block.  They must appear at the same nesting level,
+   and any variables declared after VA_OPEN go out of scope at
+   VA_CLOSE.  Unfortunately, with a K+R compiler, that includes the
+   argument list.  You can have multiple instances of VA_OPEN/VA_CLOSE
+   pairs in a single function in case you need to traverse the
+   argument list more than once.
 
    For ease of writing code which uses GCC extensions but needs to be
    portable to other compilers, we provide the GCC_VERSION macro that