[cfe-dev] Suggestion for improving #include error message
Renato Golin
rengolin at systemcall.org
Thu Oct 29 15:01:02 PDT 2009
2009/10/29 Justin Johansson <procode at adam.com.au>:
> Christian's
> suggestion re hinting -print-search-dirs would be a good idea idea (IMHO);
Agreed that the command line option can make it as verbose as
possible, assuming the user knows what he's doing.
> I don't think that would be too noisy as with missing #include
> files there is not much point outputting too many additional compile
> errors anyway (?)
This is not always the case. On big projects, compilation in multiple
threads or makefiles not stopping at the first error can bring madness
to the output and make it difficult even to know which file is
actually broken.
cheers,
--renato
Reclaim your digital rights, eliminate DRM, learn more at
http://www.defectivebydesign.org/what_is_drm
More information about the cfe-dev
mailing list