Use of angle brackets around file names for include statements

[elfring]

Would you like to replace any double quotes by angle brackets around file names for include statements?

[mattiasflodin]

Please explain why. I do not see any clearly stated reason in the Stack Overflow link you supplied.

[elfring]

I suggest to reconsider the consequences of the following wording from the section "16.2 Source file inclusion" in the standard specification for the programming language "C++".

…
The named source file is searched for in an implementation-defined manner. If this search is not supported, or if the search fails, the directive is reprocessed as if it read

#include <h-char-sequence> new-line
…

• How do you think about to avoid "a duplicated file search" here?
• Would you like to restrict the searched directories for header files of your software?

[mattiasflodin]

This is again very vague. I am closing this issue now. If you will give me a specific, practical problem that users may experience then I will consider it. Until then, I will assume that you are just deliberately wasting my time.

[elfring]

• You are using angle brackets at some source code places already in the way I suggest here. How do you think about to adjust a few other places for consistency?
• There are different opinions about the handling of the involved implementation-defined behaviour.
  • Will header files be also searched outside the specified include directories if double quotes are used for the discussed preprocessor statement?
  • Is there a speed difference measurable if a file is not found there and the search will be retried with "the angle brackets inclusion method"?