Re: #include with <> or "" ?
On Aug 1, 4:44 pm, Victor Bazarov <v.Abaza...@comAcast.net> wrote:
saneman wrote:
I have a folder 'app' containing a file 'main.cpp' and a
subfolder 'types' (containing various header files). In
main.cpp some header files from the subdir 'types' are
included like:
1)
#include<types/vector.h>
#include<types/matrix.h>
But I have to change them to
2)
#include "types/vector.h"
#include "types/matrix.h"
to make compilation work. I know that 1) worked earlier with
the original makefile but I don't have that anymore. How is
it possible to make the code compile with the version used
in 1) again?
I am currently working in MS Visual Studio 2008 and it seems
that makefiles are generated automatically.
The difference in processing of the angle-bracket type
inclusion directives and the double-quote type is
*implementation-defined*.
In theory. In practice: includes in a <> are searched first in
a list of directories that you provide (via -I or /I options,
depending on the compiler), then in some standard system places
(where the compiler is installed, then /usr/include under most
Unix; under Windows, at least with VC++, I think the contents of
the environement variable INCLUDE). An include "" first
searches in the directory where the file containing the include
was situated, and then acts exactly like an include <>.
Some compilers have additional options to modify this somewhat
(e.g. adding a directory which is only used by include ""), but
I've yet to find a compiler which didn't support the above.
--
James Kanze (GABI Software) email:james.kanze@gmail.com
Conseils en informatique orient=E9e objet/
Beratung in objektorientierter Datenverarbeitung
9 place S=E9mard, 78210 St.-Cyr-l'=C9cole, France, +33 (0)1 30 23 00 34