From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 11942 invoked by alias); 19 May 2003 06:51:10 -0000 Mailing-List: contact gcc-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Archive: List-Post: List-Help: Sender: gcc-owner@gcc.gnu.org Received: (qmail 11912 invoked from network); 19 May 2003 06:51:09 -0000 Received: from unknown (HELO uniton.integrable-solutions.net) (62.212.99.186) by sources.redhat.com with SMTP; 19 May 2003 06:51:09 -0000 Received: from uniton.integrable-solutions.net (localhost [127.0.0.1]) by uniton.integrable-solutions.net (8.12.3/8.12.3/SuSE Linux 0.6) with ESMTP id h4J6obeR013284; Mon, 19 May 2003 08:50:37 +0200 Received: (from gdr@localhost) by uniton.integrable-solutions.net (8.12.3/8.12.3/Submit) id h4J6obRk013283; Mon, 19 May 2003 08:50:37 +0200 X-Authentication-Warning: uniton.integrable-solutions.net: gdr set sender to gdr@integrable-solutions.net using -f To: Zack Weinberg Cc: gcc@gcc.gnu.org Subject: Re: Warning for trigraphs in comment? References: <87he7sdvlm.fsf@egil.codesourcery.com> From: Gabriel Dos Reis In-Reply-To: <87he7sdvlm.fsf@egil.codesourcery.com> Organization: Integrable Solutions Date: Mon, 19 May 2003 06:57:00 -0000 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-SW-Source: 2003-05/txt/msg01734.txt.bz2 Zack Weinberg writes: | Gabriel Dos Reis writes: | | > Second, consider the comment line. Did you notice that it ends oddly, | > with a "/"? | > | > // What will the next line do? Increment???????????/ | > ^ | ... | > | > is extracted from Herb's GTW #86 -- full message appended below. | > I would suggest we warn for trigraphs in comments. | | This was discussed a couple weeks back. Sorry, I missed that. | 3.4 now warns about ??/\n in a comment. I'm glad to learn that. Thanks, -- Gaby