Use of angle brackets around file names for include statements about easylambda HOT 7 CLOSED

The opinions on the SO link are quite differing. The most convincing to me is:

• double quotes when giving relative path.
• angle brackets when in include path.

There are opinions that say it helps distinguish system headers from library headers although I don't think this should be the case.

Is there anything more to it?

from easylambda.

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?

from easylambda.

I totally agree with using angular brackets in examples, tests and for any code that uses the library.

The confusion is for library headers. For e.g. ezl.hpp can have relative paths and double quotes or it can have angular brackets.

I think that its better to have angular brackets everywhere for consistency but just some clarification before going ahead. :)

from easylambda.

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"?
• How do you think about to follow the inclusion style from the class library "Boost"?

from easylambda.

I just checked with Boost 1.54 that uses double quotes everywhere and 1.60 that uses angle brackets everywhere.

Commit for using angle brackets consistently everywhere.

from easylambda.

Thanks for your source code improvement.

from easylambda.

Thanks for the very useful suggestions and informative links.

from easylambda.