This is the mail archive of the gcc-bugs@gcc.gnu.org mailing list for the GCC project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

[Bug preprocessor/29245] no way to safely attempt an #include which may fail



------- Comment #3 from pinskia at gcc dot gnu dot org  2006-09-27 04:08 -------
(In reply to comment #2)
> (In reply to comment #1)
> > Use autoconf like the GNU coding style recommends.
> 
> That is exactly the the main "gross hack" I refer to.

How is it a gross hack.  Really what you are requesting is even worse as it
only works with one compiler and looks worse.
using __FreeBSD__ or __i386__ is just as bad as anything else really.
And actually people do compile with -pedantic-errors so using your method is
worse than an autoconf as yours will not work.


-- 

pinskia at gcc dot gnu dot org changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|UNCONFIRMED                 |RESOLVED
         Resolution|                            |INVALID


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=29245


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]