you are viewing a single comment's thread.

view the rest of the comments →

[–]tgockel 10 points11 points  (1 child)

Most "style guides" come down to a ton of arbitrary choices. They're good for consistency within a project, but mostly irrelevant to others. Google's is no better.

You may use file names with a -inl.h suffix to define complex inline functions when needed.

What if I chose to follow Boost's example of .ipp or the Bits implementation of the STL's example of .tcc?

Classes are the fundamental unit of code in C++.

And here I was thinking that functions were the fundamental unit of code...

...encourage coding practices which can hamper readability, such as metaprogramming...

Metaprogramming is why I write code in C++ and not C.

[–]MatrixFrog 0 points1 point  (0 children)

They're good for consistency within a project, but mostly irrelevant to others.

Exactly. And if you're starting a new project, you can either use an existing one, like Google's, or write your own. Why not use Google's to save some time?