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

2006-09-27 Thread drow at gcc dot gnu dot org
--- Comment #5 from drow at gcc dot gnu dot org 2006-09-28 01:32 --- While I firmly agree with Wolfgang, my same comment about the meaning of "RESOLVED/INVALID" applies here also. -- drow at gcc dot gnu dot org changed: What|Removed |Added

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

2006-09-26 Thread bangerth at dealii dot org
--- Comment #4 from bangerth at dealii dot org 2006-09-27 04:30 --- This is definitely firmly in the class of "extension to the language that requires a thorough proposal to be presented to the standards committee" things. I don't think anyone is even remotely interested in implementing

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

2006-09-26 Thread pinskia at gcc dot gnu dot org
--- 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 requ

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

2006-09-26 Thread acahalan at gmail dot com
--- Comment #2 from acahalan at gmail dot com 2006-09-27 04:03 --- (In reply to comment #1) > Use autoconf like the GNU coding style recommends. That is exactly the the main "gross hack" I refer to. Hacks like autoconf should not be necessary. People also hack around the problem with cm

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

2006-09-26 Thread pinskia at gcc dot gnu dot org
--- Comment #1 from pinskia at gcc dot gnu dot org 2006-09-27 00:32 --- Use autoconf like the GNU coding style recommends. -- pinskia at gcc dot gnu dot org changed: What|Removed |Added --