Skip to main content

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

Required fields*

9
  • There is a requirement, though, that if #include "xxx" fails, the compiler reprocess it as if it had been #include <xxx>. Commented Dec 3, 2012 at 13:46
  • @James That's what I intended the third sentence to mean. Do you think I should rephrase it, or did you miss that? Commented Dec 3, 2012 at 13:47
  • +1 for googling source files :-) Commented Dec 3, 2012 at 13:58
  • I think the significant reason for the "places" being so loosely specified is that header "files" don't have to be actual files, let alone in an actual filesystem. You could write a conforming C++ implementation over some kind of version control or whatnot, just as long as it can figure out what bytes the nominal "file" contains. And of course in practice both locations depend on command-line options. Commented Dec 3, 2012 at 14:16
  • @SteveJessop, yeah wouldn't it be nice to be able to include different revisions of the same file from mercurial, or whatever vcs.. %) #include "MyClass.h.99fdadcf54" Commented Dec 3, 2012 at 14:28