| 29 May 2015 | ||
| 08:30:30 | FireFury | dom: it's supported by GCC, but slightly stupidly you also get "warning: #warning is a GCC extension" whenever you use #warning, even though I've set the standard to gnu99 instead of c99 |
| 08:19:28 | FireFury | wonders why #warning isn't a standard C99 thing |
| 17 Sep 2014 | ||
| 14:41:08 | FireFury | WTF does GCC feel the need to tell me that #warning is a GCC extension? |
| 15 Feb 2012 | ||
| 09:32:02 | tswsl1989 | That would stop it paying attention to #warning, not warning about #warning |
| 09:25:03 | FireFury | tries to figure out if its possible to tell gcc to stop warning him about #warning being a gcc extension |
| 02 Feb 2012 | ||
| 16:16:18 | FireFury | is there a C99 equivalent of #warning ? |
| 22 Feb 2010 | ||
| 16:37:25 | sits | flagg: /usr/lib64/gcc/x86_64-slackware-linux/4.3.3/../../../../include/c++/4.3.3/backward/backward_warning.h:33:2: warning: #warning This file includes at least one deprecated or antiquated header which may be removed without further notice at a future date. Please use a non-deprecated interface with equivalent functionality instead. For a listing of replacement headers and interfaces, consult the file backward_warning.h. To disable this warning use -Wno-deprecated. |
| 16 Mar 2009 | ||
| 12:41:10 | FireFury | #warning |
