Is there any standard order of inclusion to avoid hidden dependencies?

Question

if yes,is this correct order?

C library headers
C++ library headers
Other library headers
Related headers
our projects headers

Always include your own header first - so `foo.cc` includes `foo.hh` first. That ensures that `foo.hh` is self-contained and does not depend on `foo.cc` including other headers for it. — Jesper Juhl, Jul 05 '16 at 11:38

score 4 · Accepted Answer · answered Jul 05 '16 at 11:34

There is no standard order, but if you want to avoid hidden dependencies, you have to go in the exact opposite order: include the most project-specific headers first, then specific library headers, then more generic library headers (such as e.g. Qt and boost), and eventually standard library headers last.

This way, you will be certain that missing dependencies of your project's headers are not accidentally satisfied by the headers which you've included earlier.

Is there any standard order of inclusion to avoid hidden dependencies?

1 Answers1