This is the mail archive of the gcc@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: Plugin that parse tree

From: Ian Lance Taylor <iant at google dot com>
To: Daniel MarjamÃki <daniel dot marjamaki at gmail dot com>
Cc: gcc at gcc dot gnu dot org
Date: Mon, 24 Jan 2011 12:55:17 -0800
Subject: Re: Plugin that parse tree
References: <ed10e8adfd7ebb41d2f361b2a06c2e11@localhost> <95f62d57256fbc424a68e891a679b390@localhost> <AANLkTi=WqRt4hOYs79dNe3_t67iC5xWDqTdx_5xPP3Mu@mail.gmail.com> <mcr8vya9u9h.fsf@google.com> <AANLkTi=ao9h-zv1tqqce+WN=1zY3qcFh2b5kXb19oy2p@mail.gmail.com>

Daniel MarjamÃki <daniel.marjamaki@gmail.com> writes:

> 2011/1/24 Ian Lance Taylor <iant@google.com>:
>
>> The problem with warnings for this kind of code in C/C++ is that it
>> often arises in macro expansions.
>
> I see... so it won't be included in gcc. :-(

Actually, I think it could be included in gcc, provided you (or
somebody) first implements a way to not warn in a macro expansion.

Ian

Follow-Ups:
- Re: Plugin that parse tree
  - From: Daniel Marjamäki

References:
- Re: Plugin that parse tree
  - From: piervit
- Re: Plugin that parse tree
  - From: Daniel Marjamäki
- Re: Plugin that parse tree
  - From: Ian Lance Taylor
- Re: Plugin that parse tree
  - From: Daniel Marjamäki

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