From: "Laurynas Biveinis" <lauras AT softhome DOT net>
Date: Sat, 14 Jul 2001 23:22:04 +0200
To: djgpp AT delorie DOT com
Subject: Re: RHIDE using gcc 3.0 problem
Message-ID: <20010714232204.B211@lauras.lt>
References: <1103_995126900 AT default>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <1103_995126900@default>
User-Agent: Mutt/1.3.18i
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
Precedence: bulk


> #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.

Laurynas