From c864312278d46ec2a65bec64f6eef53be1b5a0e9 Mon Sep 17 00:00:00 2001 From: "Kaveh R. Ghazi" Date: Wed, 29 Aug 2001 19:44:39 +0000 Subject: * ansidecl.h: Update comments reflecting previous change. From-SVN: r45275 --- include/ChangeLog | 4 ++++ include/ansidecl.h | 12 +++++++----- 2 files changed, 11 insertions(+), 5 deletions(-) diff --git a/include/ChangeLog b/include/ChangeLog index 23ba4fb..81d2cc2 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 -- cgit v1.1