header flies
I have one doubt that why some of the header files are inside this <_> (Arrows)and some of the some of header files are inside this "_" (Inverted commas). What if we interchange the Header files that means interchange arrow with inverted commas.
please explain me in detail. thank you.
Please help me in this and thanks in advance
please explain me in detail. thank you.
Please help me in this and thanks in advance
I believe
Here's the question/answer on StackOverflow: http://stackoverflow.com/questions/21593/what-is-the-difference-between-include-filename-and-include-filename
#include <x.h> looks for the header file in your IDE folders, while #include "x.h" looks for the header file in your current project's folder.Here's the question/answer on StackOverflow: http://stackoverflow.com/questions/21593/what-is-the-difference-between-include-filename-and-include-filename
Last edited on
this one is tricky :)
first, you have a question. A doubt is something else in most forms of English.
Second, <> are often called angle brackets in code.
Third, "" are quotation marks.
<a.h> --- this is one of 2 things. This is either a built-in header file, like <vector> or <cstdlib> etc, which is part of the language, or it is a project defined folder. I strongly dislike the use of <> for anything that is NOT part of the language, personally, but some developers do this. It makes code fail to compile if you don't define the same setup, which is an extra step and totally unnecessary.
"a.h" is an explicit path. the compiler will look in any paths you gave it if you left the path off, starting at some default path that is usually where the code lives. If it is not in your project's simple path, I prefer to use the full or relative path to it:
"/folder/deeper/a.h" for example.
This is just as annoying -- if you fully qualify it, for example
"c:\somefolderonlyIhave\whatamess\a.h"
your poor user has to either fix it or create that folder structure exactly, and simply moving the code breaks it. Try to use relative paths!
first, you have a question. A doubt is something else in most forms of English.
Second, <> are often called angle brackets in code.
Third, "" are quotation marks.
<a.h> --- this is one of 2 things. This is either a built-in header file, like <vector> or <cstdlib> etc, which is part of the language, or it is a project defined folder. I strongly dislike the use of <> for anything that is NOT part of the language, personally, but some developers do this. It makes code fail to compile if you don't define the same setup, which is an extra step and totally unnecessary.
"a.h" is an explicit path. the compiler will look in any paths you gave it if you left the path off, starting at some default path that is usually where the code lives. If it is not in your project's simple path, I prefer to use the full or relative path to it:
"/folder/deeper/a.h" for example.
This is just as annoying -- if you fully qualify it, for example
"c:\somefolderonlyIhave\whatamess\a.h"
your poor user has to either fix it or create that folder structure exactly, and simply moving the code breaks it. Try to use relative paths!
Last edited on
Topic archived. No new replies allowed.