Need a way to indicate that one header depends on the macros in another header

[mydogisbox]

I have two headers where one header depends on the macros defined in the other header, but the second header doesn't include the first header. The assumption is that the first header will always be included in a file before the second header. As a result, I'm getting errors in the second header.

Currently I am resolving this issue by creating a third header which includes the other two headers in the appropriate order. It would be nice to have some way of indicating this dependency in code rather than having to create another header.

[tritao]

That's a pretty bad practice for public headers, each header should always include enough headers so that it can be used in a standalone way.

Anyway, I could add a way so you can specify extra pre-includes per input header. Would that work for you?

[Dzonatas]

Standard C++ puts inline code in .hpp and then includes .hpp files in each .h for working with both .cpp and .c semantics or precedence. File.cpp, File.c, File,.hpp, File.h ; you should be able to tab through easily in Eclipse C/C++. Makes working with thousands of source files much easier, in practice (unless you have sticky contracts).

[mydogisbox]

It confused me the first time I saw it for sure. I would probably change it if this was something I had written. Extra pre-includes would be great.

[tritao]

I suggest just creating a new header file that includes the ones you need, or fixing the original code.