From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 11501 invoked by alias); 14 Oct 2006 18:08:31 -0000 Received: (qmail 11459 invoked by alias); 14 Oct 2006 18:08:22 -0000 Date: Sat, 14 Oct 2006 18:08:00 -0000 Message-ID: <20061014180822.11458.qmail@sourceware.org> X-Bugzilla-Reason: CC References: Subject: [Bug c++/29455] Issues with -Wchar-subscripts In-Reply-To: Reply-To: gcc-bugzilla@gcc.gnu.org To: gcc-bugs@gcc.gnu.org From: "pinskia at gmail dot com" Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Archive: List-Post: List-Help: Sender: gcc-bugs-owner@gcc.gnu.org X-SW-Source: 2006-10/txt/msg01247.txt.bz2 List-Id: ------- Comment #4 from pinskia at gmail dot com 2006-10-14 18:08 ------- Subject: Re: Issues with -Wchar-subscripts On Sat, 2006-10-14 at 17:52 +0000, h dot b dot furuseth at usit dot uio dot no wrote: > > Also you forgot one thing '%' does not have to match up with the ANSI > > character set so it could be negative in signed char which means char > > (which could default to signed char) would be different. > > No. In a conforming C implementation, the character *which C interprets > as '%'* must have a positive value. Maybe you are thinking of the > opposite case: What its glyph _looks like_ on some display device is out > of scope for the C standard. But at this point, we are talking about C++ where 'a' is of type char. I have to look at what the C++ standard says about this. -- Pinski -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=29455