On Wed, 19 Mar 2008 18:04:20 -0800, Carmen Sei <email@example.com>
For non-absolute paths, the quoted form begins the search in the directory
of the file making the #include and falls back to the angle-bracket form if
it doesn't find the file there. For more, see:
The #include Directive
Actually, I see now there's an extra step (2):
1. In the same directory as the file that contains the #include statement.
2. In the directories of any previously opened include files in the reverse
order in which they were opened. The search starts from the directory of
the include file that was opened last and continues through the directory
of the include file that was opened first.
3. Like the angle brackets.
I would not recommend taking advantage of (2), because to rely on it is to
put yourself at the mercy of whomever #includes you. It seems to me it's a
recipe for ambiguity.
Visual C++ MVP