This is the mail archive of the gcc-help@gcc.gnu.org mailing list for the GCC project.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]
Other format:	[Raw text]

Re: best practice to handle unused variables depending on macros

From: Jonathan Wakely <jwakely dot gcc at gmail dot com>
To: Mathieu Lacage <mathieu dot lacage at gmail dot com>
Cc: gcc-help <gcc-help at gcc dot gnu dot org>
Date: Mon, 6 Feb 2012 19:03:03 +0000
Subject: Re: best practice to handle unused variables depending on macros
References: <CAOV_JPaqhPJjHg1VAWcatuq0FRmiRpHiZ2BHJJ6qi44=pCDU4A@mail.gmail.com> <CAH6eHdQ=-_MysuD8DyKJrECebn8W4EPps3M+n0bYZbyYwMzsdA@mail.gmail.com> <CAOV_JPaeT6ox6wjQTX1SmF7tN8EsYCYdapbmkhNF3-LuUXAxmQ@mail.gmail.com>

On 6 February 2012 18:15, Mathieu Lacage wrote:
> Out of curiosity, would (void)sizeof(a) work with non-gcc compilers ?

What do you mean "work"?

It's valid C, so any compiler will accept it and not evaluate the
expression.  If you mean "will it suppress an unused variable warning"
I don't know.

Follow-Ups:
- Re: best practice to handle unused variables depending on macros
  - From: Mathieu Lacage

References:
- best practice to handle unused variables depending on macros
  - From: Mathieu Lacage
- Re: best practice to handle unused variables depending on macros
  - From: Jonathan Wakely
- Re: best practice to handle unused variables depending on macros
  - From: Mathieu Lacage

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]