> > Shouldn't the generated #includes be to <file.h> instead of "file.h"? > > You're always generating the path relative to the compiler's set of > > include directories, not relative to the current directory. > > I thought that <file.h> was for system headers and "file.h" was for 'my' > headers. I could be wrong...
There's not much difference... The "foo.h" form adds the current directory to the head of the include search path, while the <foo.h> doesn't. So "foo.h" was kind of for "your" headers, back when C programs were simple and all the files lived in the same directory, because #include "foo.h" meant, include this other file called "foo.h" in this directory. Since you're not using that feature, probably better to use the <foo.h> form. > All the bugs you found today are the so-called second use bugs. Happy to help :-). Bill _______________________________________________ pylucene-dev mailing list [email protected] http://lists.osafoundation.org/mailman/listinfo/pylucene-dev
