[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Bug in #include guards

From: Akim Demaille
Subject: Re: Bug in #include guards
Date: 02 Oct 2001 19:01:55 +0200
User-agent: Gnus/5.0808 (Gnus v5.8.8) XEmacs/21.4 (Artificial Intelligence)

>>>>> "Alexander" == Alexander Belopolsky <address@hidden> writes:

Alexander> Akim Demaille writes:
>>  I'm applying this, thanks.
Alexander> <snip>
>> + for (cp = macro_name; *cp; ++cp) + if (islower (*cp)) + *cp =
>> toupper (*cp);
Alexander> <snip> In addition to my previous comment, I believe that
Alexander> upcasing all macro_name character is not a good idea for
Alexander> the same reason: include guards should be different in
Alexander> different file names.

If you have several pathnames mapping to the same UPPER_CASE_GUARD,
you are asking for problems by yourself.  Then, just don't depend on
these guard, and use a header yourself too.  After all, proper use of
Bison makes this feature absolutely useless.  That was done to please
users, not to solve an actual problem.

reply via email to

[Prev in Thread] Current Thread [Next in Thread]