[cfe-dev] -Wheader-guard emits warning after #undef of guard macro

[Richard Trieu]

On Mon, Jan 13, 2014 at 3:06 AM, Prathamesh Kulkarni <
bilbotheelffriend at gmail.com> wrote:

> For the following test-case:
> #ifndef FOO
> #define FOO2
>
> #undef FOO2
> #endif
>
> -Wheader-guard emits warning:
> ./foo.h:4:9: warning: 'FOO' is used as a header guard here, followed
> by #define of a different macro [-Wheader-guard]
> #ifndef FOO
>         ^~~
> ./foo.h:5:9: note: 'FOO2' is defined here; did you mean 'FOO'?
> #define FOO2
>         ^~~~
>
> Is this appropriate or should it suppress warning in this case
> since it's equivalent to the following: ?
> #ifndef FOO
> #endif
>
> Thanks and Regards,
> Prathamesh
> _______________________________________________
> cfe-dev mailing list
> cfe-dev at cs.uiuc.edu
> http://lists.cs.uiuc.edu/mailman/listinfo/cfe-dev
>

Oops, forgot to include the mailing list.  Sorry for the double email,
Prathamesh.

Prathamesh,

Can you tell me more about your use case?  Is this a common pattern you
have encountered?

The header guard warning triggers on files with the following format:

// Start of file
#ifndef Macro1
#define Macro2
...
#endif // matches the #ifndef on the first line.
// End of file

and warns when Macro1 and Macro2 are close, but not exactly the same.  The
warning already ignores cases where Macro1 and Macro2 are very different
(edit distance is over half the length).  A similar exemption maybe be
warranted in this case too.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.llvm.org/pipermail/cfe-dev/attachments/20140113/602453b1/attachment.html>