Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
When you write #include "foo.h" I would expect the compiler to check the directory of the file doing the including (as opposed to the current directory) first, and if not found there then fall back on a search of the list of paths as in the case of #include <foo.h>.
Unless an absolute path was specified, #include "/foo.h", in which case only the absolute path needs to be checked.
Are there any C compilers where the rules are different?
Kernighan & Ritchie write:
Which means, make no assumption on the search strategy for quotes. However, all compilers I have run into share the praxis of searching in the including file’s path first, and falling back to the compiler’s search path if not found.