This is the mail archive of the
gcc-patches@gcc.gnu.org
mailing list for the GCC project.
Re: Preprocessor and -C / -CC
- To: Zack Weinberg <zack at wolery dot cumb dot org>
- Subject: Re: Preprocessor and -C / -CC
- From: Jason R Thorpe <thorpej at zembu dot com>
- Date: Wed, 10 May 2000 16:39:31 -0700
- Cc: Neil Booth <NeilB at earthling dot net>, gcc-patches at gcc dot gnu dot org
- Organization: Zembu Labs, Inc.
- References: <E12pUR3-0006D7-00@monkey.rosenet.ne.jp> <20000510162710.E21854@wolery.cumb.org>
- Reply-To: thorpej at zembu dot com
On Wed, May 10, 2000 at 04:27:10PM -0700, Zack Weinberg wrote:
> I've been trying to decide if this is the right behavior or not,
> myself. I definitely think comments inside the macro body should
> appear only where the macro is expanded, but I'm not sure about
> something like
>
> #define foo(a, b) bar(a, b, 12) /* default argument form of bar */
>
> the comment might be more useful if it appeared where the #define was,
> and _not_ where foo() is expanded. Jason, what would lint want?
Well, in the cccp version of CPP, the comments appeared where the
macro was defined with -C, and with the NetBSD-added -CC option,
it appeared both where the macro was defined, and where the macro
was expanded.
Lint doesn't particular care about it appearing where it is defined,
but it is absolutely required for it to appear where it is expanded,
hence -CC (we didn't feel changing the behavior of -C was necessarily
a good thing as some people might have expected that behavior).
--
-- Jason R. Thorpe <thorpej@zembu.com>