Use of angle brackets around file names for include statements

[Markus Elfring]

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

[Peter Goldsborough]

Interesting, I figure that technically it would make more sense for a library like this one to use angle brackets since the files will most likely not be in the same directory. In practice I've never found it to be an issue and I like the visual distinction of <standard> vs. "mine.h". What's your opinion?

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

[Peter Goldsborough]

Replaced #include "..." with #include <...>

[Markus Elfring]

Which commits will contain corresponding changes?

[Peter Goldsborough]

Forgot to push the commit back then. Thanks.

[Markus Elfring]

Thanks for your source code adjustment.