Date:	Mon, 16 Jul 2001 21:08:52 +0300 (WET)
From:	Andris Pavenis <pavenis AT lanet DOT lv>
To:	Laurynas Biveinis <lauras AT softhome DOT net>
Cc:	djgpp AT delorie DOT com
Subject:	Re: RHIDE using gcc 3.0 problem
In-Reply-To:	<20010714232204.B211@lauras.lt>
Message-ID:	<Pine.A41.4.05.10107162105001.54288-100000@ieva06.lanet.lv>
MIME-Version:	1.0
Reply-To:	djgpp AT delorie DOT com
Errors-To:	nobody AT delorie DOT com
X-Mailing-List:	djgpp AT delorie DOT com
X-Unsubscribes-To:	listserv AT delorie DOT com

On Sat, 14 Jul 2001, Laurynas Biveinis wrote:

> 
> > #include <stdlib.h>
> > #include <stdio.h>
> > int main(void)
> > {
> >   printf("???!");
> >   return 1;
> > }
> > 
> > using -Wall, e.g. gcc -c -Wall test.c.
> > Results under RHIDE in an error-message
> >    test.c:6 Error:12: warning: trigraph ??! ignored
> > and compiling is stoped.
> > 
> > 
> > Beside this, what means this warning. Trigraph's in
> > a string? But this behavior isn't new with gcc 3.0.
> > Also older versions show this, but as a really
> > warning.
> 
> First of all, is this really the exact command line? I think
> the behaviour you desribe can be triggered only with -pedantic
> -Werror. At least -Werror _should_ be there, according to
> the compiler output. Trigraphs are in C language for hysterical
> reasons - the character sets in some older computers did not
> have symbols like [ ] { } etc required for C. Trigraphs replace
> them.
> 

RHIDE parses output of gcc to stderr and tries to interpret it.
It is perhaps interpretted in a incorretctly in this case.

Perhaps it would be better to simply use return code from GCC 
to find whether errors are detected. Maybe I'll change that 
sometime.

Andris

- Raw text -