Are pathnames in includes nonstandard? Because at least on Unixoid OSes, the #include "engine.h" could be solved by making the includes non-recursive, and then explicitly stating #include "A/engine.h" and #include "B/engine.h".

@dascandy

7 жыл бұрын

It's standard and it uses that too to see if they are ambiguous. It even looks for a local "engine.h" before claiming it ambiguous - if you use quotation mark includes. If you somehow made it clear which one it is, it won't flag it as ambiguous. Yet many large projects have multiple of these ambiguous includes; up to hundreds or thousands for big projects.