This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
Re: Preprocessor keyword #echo is missing
"J. Grant" <now3d@gmx.net> writes:
> while #warning is a work around, it means the text i want outputing
> during the compilation is not.
Er? You should get exactly what you put after #warning in the warning
message. With "warning: " in front of it, true - is that what you're
unhappy about?
In general we have a preference not to add more extensions to GCC;
many of us are of the opinion that there are already too many.
Particularly when the suggestion is to add a new directive, I would
want to see a thoroughly compelling rationale for it - that means
something that you can do with it that there's no other way to do.
Also, a good reason why it should be spelled #echo and not #notice or
#pragma GCC message "string constant" or something like that, would be
nice.
What other compilers are you familiar with that support #echo?
zw