Default include about cppitertools HOT 4 CLOSED

I'm not so sure this is a real issue, it's a library you should be adding the include path, especially considering there are several dependencies. Anyway if you really want to use components by themselves you can just change it yourself. Just for a reference boost uses all <> includes in their hpp files

from cppitertools.

This is not entirely accurate. boost mixes the use of "" and <>. However, this is not the point. If you look at boost's include files, you will notice that each include is either relative to the current directory (using a "") or a relative to the include path (using <>). All absolute includes make sure to prefix the path with 'boost/', which enables a user to only add the boost include dir to her include path.

In other words, using your current convention, if I am to use your library and place it at /usr/local/include/cppitertools, I have to explicitly add this directory to my incelude path and must include your library using
#include <itertools.hpp>

However, if you change your include scheme to prefix each include with "cppitertoold/", I can drop the library in /usr/local/include and, as this library is already in my include path, only use the following:

#include <cppitertools/itertools.hpp>

Am I making sense?

from cppitertools.

yes this is a good explanation. I'll look around to see what the best way to handle it would be and take a closer look at boost. thanks

from cppitertools.

Given we don't have a defined based directory name, the "" includes will allow for flexible including so I've made the changes. Thanks for your interest

from cppitertools.