> > Then how about an option to make any warning (or at least those warnings)
> > be treated as an error? Otherwise, it's just too easy to overlook
> > the warnings in the reams of usual output.
>
> If someone is not looking at the output and wants to see warnings
> nevertheless,
> he can use the option '--quiet' or even '--quiet --quiet'.
Another option is to use a terminal which displays stderr output in a different
colour than stdout output, in red for example. I think 'colorgcc' can do this,
some terminal emulators as well, I guess. I've been using this tiny hack
sometimes (works only in unibyte locales, though).
Bruno
============================== red.c =================================
#include <unistd.h>
int main()
{
char c[] = { 27, '[', '3', '1', 'm', 0, 27, '[', '3', '9', 'm' };
for (;;) {
if (read(0,c+5,1) <= 0) break;
write(1,c,11);
}
return 0;
}
/*
* Utilisation 1:
* $ command 2> >(red)
* Utilisation 2:
* $ mkfifo /tmp/red1
* $ red < /tmp/red1 &
* $ command 2> /tmp/red1
*/
=====================================================================
