Re: [boost] #ifndef paradigm

From: Victor A. Wagner, Jr. (vawjr_at_[hidden])
Date: 2002-08-28 11:05:08

At Tuesday 2002/08/27 11:58, you wrote:
>Often, when one wants to make sure a header is included only once, s/he uses
>the paradigm:
>
>#ifndef HEADER_NAME_H__
>#define HEADER_NAME_H__
>
>// code here...
>
>#endif // HEADER_NAME_H__ -- this comment is to make it clear what the endif
>is for
>
>
>It is better to remove the duality of the comment at the end, by switching
>to this paradigm:

unless, of course, you have mutually inclusive files.  Then it's possible 
to make the above work, but not what follows.

>#ifndef HEADER_NAME_H__
>
>// code here...
>
>#define HEADER_NAME_H__
>#endif
>
>
>When maintiaining a file -- renaming it -- with the comment, one has to make
>sure the comment is also updated. This alternative removes the comment
>because it is superfluous, and the compiler will help you if you forget to
>change the #define at the end.
>
>_______________________________________________
>Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost

Victor A. Wagner Jr.      http://rudbek.com
PGP RSA fingerprint = 4D20 EBF6 0101 B069 3817 8DBF C846 E47A
PGP D-H fingerprint = 98BC 65E3 1A19 43EC 3908 65B9 F755 E6F4 63BB 9D93
The five most dangerous words in the English language:
               "There oughta be a law"