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?

[markcharney]

Not so sure about this one. Is this really necessary?

[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?

[rscohn2]

Markus, After reading https://gcc.gnu.org/onlinedocs/cpp/Include-Syntax.html, I think "" is correct. It allows xed-interface.h to find the other header files in the current directory, even if they are not in the system include area or user does not use -I<path-to-xed>. It also prevents issues where xed-interface.h is in a private directory, but incorrectly pulls in the rest of the header files from a system dirctory. Robert

…

On Fri, Dec 23, 2016 at 1:34 AM, Markus Elfring ***@***.***> wrote: I suggest to reconsider the consequences of the following wording <http://c0x.coding-guidelines.com/6.10.2.html> from the section "16.2 Source file inclusion" <http://open-std.org/jtc1/sc22/wg21/docs/papers/2013/n3797.pdf> 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 <https://gcc.gnu.org/onlinedocs/cpp/Include-Syntax.html> for header files of your software? — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub <#22 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AB2NWr5ea5Nlq08AkHQgpsc2-AdbU3ghks5rK2t3gaJpZM4LUXKN> .

[elfring]

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”?