-
Notifications
You must be signed in to change notification settings - Fork 203
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Make #includes match C++ Core Guidelines #80
Comments
When this is addressed, the include strategy in |
Yeah Unreal gets really grumpy when we include Windows header. I don't think changing the order of includes will solve it, because source code using Unreal types has issues too, it's not just the Unreal headers that are a problem. In general we shouldn't have any reason to include windows.h in any header. Unreal has portable versions of most of what we'd want to use from windows.h anyway. If we need something unusual, including windows.h in a .cpp that doesn't depend on Unreal is fine. The reason we ran into problems with spdlog is because it has weird defaults that make it so that I'm mostly writing this down for future reference, because it was a pain to figure out. |
I've changed the title to reflect the fact that the action here is to move cesium-native to the include strategy recommended in the C++ Core Guidelines: https://isocpp.github.io/CppCoreGuidelines/CppCoreGuidelines#sf12-prefer-the-quoted-form-of-include-for-files-relative-to-the-including-file-and-the-angle-bracket-form-everywhere-else More detail here: #56 (comment) |
We've now done this, more or less. We should write issues for any remaining issues as we find them (or just fix them), but we can close this issue. |
There currently are some subtle inconsistencies regarding
include
directives. Specifically, the pattern of brackets/quotes for<system_includes>
and"own_includes"
is not applied consistently. The relevant comment that summarizes this is at #56 (comment)This should be fixed, preferably in one, dedicated cleanup step.
The text was updated successfully, but these errors were encountered: