Re: [Widelands-public] Time to make up our mind about include guard naming

[Aggro <ag...@pp...>]

Erik wrote:
> There is a great diversity of include guard name patterns. Some examples:
> #ifndef included_ui_tabpanel_h

I've never before seen anyone using lower case include guards before. So 
not this one.

> #ifndef __S__UNIQUE_WINDOW_H

This is against the C++ standard (double underscore in names is reserved 
for the implementation), so not this.

> #ifndef __CAMPVIS_H

This is against the C++ standard, so not this.

> #ifndef FILEREAD_H

This is good.

--