Portability of #warning preprocessor directive

c++ compiler-construction warnings c-preprocessor portability
jonner picture jonner · Oct 5, 2008 · Viewed 41.2k times · Source

I know that the #warning directive is not standard C/C++, but several compilers support it, including gcc/g++. But for those that don't support it, will they silently ignore it or will it result in a compile failure? In other words, can I safely use it in my project without breaking the build for compilers that don't support it?

Answer

nolandda picture nolandda · Nov 11, 2008

It should be noted that MSVC uses the syntax:

#pragma message ( "your warning text here" )

The usual #warning syntax generates a fatal error 

C1021: invalid preprocessor command 'warning'

so it is not portable to those compilers.

Related questions

"No newline at end of file" compiler warning

What is the reason for the following warning in some C++ compilers? No newline at end of file Why should I have an empty line at the end of a source/header file?

Read More
How to disable #pragma warnings?

While developing a C++ application, I had to use a 3rd party library which produced a huge amount of warnings related with a harmless #pragma directive being used. ../File.hpp:1: warning: ignoring #pragma ident In file included from ../File2.hpp:47, …

Read More
C / C++ compiler warnings: do you clean up all your code to remove them or leave them in?

I've worked on many projects where I've been given code by others to update. More often than not I compile it and get about 1,000+ compiler warnings. When I see compiler warnings they make me feel dirty, so my first task …

Read More