Patch installed updating comments for ansidecl.h VA_* macros

[Kaveh R. Ghazi]

This patch updates the comments in ansidecl.h regarding the VA_*
macros as per the changes in my previous patch.

It takes out the sentence which said statements could not appear
before VA_OPEN and adds a sentence that multiple instances are allowed
in a single function.

Installed as `obvious'.

		--Kaveh


Index: ChangeLog
===================================================================
RCS file: /cvs/gcc/gcc/include/ChangeLog,v
retrieving revision 1.92
diff -u -p -r1.92 ChangeLog
--- ChangeLog	2001/08/27 19:10:39	1.92
+++ ChangeLog	2001/08/29 19:44:13
@@ -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.
Index: ansidecl.h
===================================================================
RCS file: /cvs/gcc/gcc/include/ansidecl.h,v
retrieving revision 1.12
diff -u -p -r1.12 ansidecl.h
--- ansidecl.h	2001/08/27 19:10:39	1.12
+++ ansidecl.h	2001/08/29 19:44:13
@@ -93,11 +93,13 @@ Foundation, Inc., 59 Temple Place - Suit
 
 
    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