[Octave-bug-tracker] [bug #41027] config.h is too generic

[Rik]

Follow-up Comment #30, bug #41027 (project octave):

I suppose we could, in the sense that the tools support it, but it seems weird
to use #include <...> when the headers are not from system libraries.  I use
the difference in syntax between <lib.h> and "lib.h" as a hint to the
programmer about the structure of the code.

There is a whole Stack Overflow thread on this:
http://stackoverflow.com/questions/21593/what-is-the-difference-between-include-filename-and-include-filename.

In short, it seems that for gcc the difference is that #include "..." will
look first in the directory where the source code is being compiled.  It seems
very unlikely that a stray config.h is going to appear in, for example,
libinterp/corefcn/.  Certainly 'make dist' will not include it.  Even at the
top-level of the source tree where a config.h might accidentally get created,
I don't think there is much danger.  As far as I can see there is no actual C
or C++ file at the top-level that--being compiled--would attempt to include
config.h


    _______________________________________________________

Reply to this item at:

  <http://savannah.gnu.org/bugs/?41027>

_______________________________________________
  Message sent via/by Savannah
  http://savannah.gnu.org/