From: DJ Delorie Date: Wed, 29 Aug 2001 20:03:08 +0000 (+0000) Subject: merge from gcc X-Git-Tag: cygnus_cvs_20020108_pre~1499 X-Git-Url: http://review.tizen.org/git/?a=commitdiff_plain;h=f2e55dc2f46c3c562187f1aef93dc0cf865b3f0a;p=external%2Fbinutils.git merge from gcc --- diff --git a/include/ChangeLog b/include/ChangeLog index 640b058..24541e0 100644 --- a/include/ChangeLog +++ b/include/ChangeLog @@ -1,3 +1,7 @@ +2001-08-29 Kaveh R. Ghazi + + * ansidecl.h: Update comments reflecting previous change. + 2001-08-27 Kaveh R. Ghazi * ansidecl.h (VA_OPEN, VA_CLOSE): Allow multiple uses. diff --git a/include/ansidecl.h b/include/ansidecl.h index 4c63fa6..9a7c577 100644 --- 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