File naming conventions about grid

[coppolachan]

In case you are renaming, do you agree in .h -> .hpp ?
Just because emacs like it for c++ styling... no stronger motivation, besides maybe separating eventual C files that could come in the future.

[paboyle]

I'm not so keen on .hpp -- it's more characters and less common; what are the features emacs enables that it does not for .h?

https://isocpp.org/wiki/faq/coding-standards#src-file-ext

"
If you already have a convention, use it. If not, and if you don’t need your editor to distinguish between C and C++ files, simply use .h. Otherwise use whatever the editor wants, such as .H, .hh, or .hpp.

We’ve tended to use either .h or .hpp for our C++ header files.
"

So, it doesn't seem to me that .h is in any way bad practice by any means, and it is certainly what I'm used to, and I'd need to understand an advantage in changing.

The web site has some really good links and some hilarious quotable paragraphs!

"
A word of warning: Nearly every software engineer has, at some point, been exploited by someone who used coding standards as a “power play.” Dogmatism over minutiae is the purview of the intellectually weak. Don’t be like them. These are those who can’t contribute in any meaningful way, who can’t actually improve the value of the software product, so instead of exposing their incompetence through silence, they blather with zeal about nits. They can’t add value in the substance of the software, so they argue over form. Just because “they” do that doesn’t mean coding standards are bad, however.

Another emotional reaction against coding standards is caused by coding standards set by individuals with obsolete skills. For example, someone might set today’s standards based on what programming was like N decades ago when the standards setter was writing code. Such impositions generate an attitude of mistrust for coding standards. As above, if you have been forced to endure an unfortunate experience like this, don’t let it sour you to the whole point and value of coding standards. It doesn’t take a very large organization to find there is value in having consistency, since different programmers can edit the same code without constantly reorganizing each others’ code in a tug-of-war over the “best” coding standard."

[coppolachan]

i agree. The only thing that made me decide to move to .hpp for IroIro was the fact that the c++ syntax is automatically highlighted for .hpp while for .h I have to change manually (lazy to hack emacs for that, although I think it is simple). No more reason than that. I don't mind so much.

[paboyle]

Global edit complete...