Re: Use of config.h: summary of responses.

[Dale Mellor]

Ralf Corsepius writes:
 > On Mon, 2004-09-13 at 11:40, Dale Mellor wrote:
 > > For the record...
 > > 
 > >    I recieved about half a dozen responses to this and the overriding
 > > message is: config.h is worse than useless for packages which install
 > > libraries and public header files, so don't use it
 > 
 > That's FUD.
 > 
 > The essence is: Don't install config.h headers. They are not designed
 > nor supposed to be installed. If you nevertheless insist on installing
 > then, you are on your own.
 > 
 > Sorry, if this sounds like ranting, but ...

   But if you can't install them, you can't include them in your
   public headers. If you can't include them in public headers they
   have to be written to a base-level platform (e.g. no use of const
   keyword), but then the sources have to be written the same
   way... etcetera, etcetera. Result: can't use config.h consistently
   anywhere. On the flip side: if you install config.h, it is not you
   that is on your own, but you are making life difficult for all
   other package developers.

   Upshot: don't use config.h.