Add include ordering rule to styleguide

[LB--]

The goal is to reduce header coupling so that each file has to include the header it needs and it can't get them by being included from other files.

For instance, a scenario to avoid:

//Class.cpp
#include <cstdint>
#include "OtherClass.hpp"
//...

//OtherClass.hpp
//...
std::uint8_t blah; //works due to include order (bad)
//...

EDIT: Also, it's pretty ugly and annoying to use "get" and "set" in the names of getter and setters - it should be obvious that they either get or set data, you don't want to type that every time.

[LB--]

I've reverted the g/s change. Any opposition to the header include order?

[Thumperrr]

No opposition. That seems like a fair style guide.

-Stephen Hall

On May 6, 2013, at 11:22 PM, "LB--" notifications@github.com wrote:

I've reverted the g/s change. Any opposition to the header include order?

—
Reply to this email directly or view it on GitHub.