From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 23960 invoked by alias); 6 Jul 2007 23:26:54 -0000 Received: (qmail 23951 invoked by uid 22791); 6 Jul 2007 23:26:53 -0000 X-Spam-Check-By: sourceware.org Received: from viper.snap.net.nz (HELO viper.snap.net.nz) (202.37.101.8) by sourceware.org (qpsmtpd/0.31) with ESMTP; Fri, 06 Jul 2007 23:26:48 +0000 Received: from kahikatea.snap.net.nz (127.63.255.123.dynamic.snap.net.nz [123.255.63.127]) by viper.snap.net.nz (Postfix) with ESMTP id 57B4D3D981D; Sat, 7 Jul 2007 11:26:45 +1200 (NZST) Received: by kahikatea.snap.net.nz (Postfix, from userid 1000) id E802E8FBF6; Sat, 7 Jul 2007 11:26:37 +1200 (NZST) From: Nick Roberts MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <18062.53164.289297.754954@kahikatea.snap.net.nz> Date: Fri, 06 Jul 2007 23:26:00 -0000 To: Eli Zaretskii Cc: Daniel Jacobowitz , gdb-patches@sourceware.org Subject: Re: [RFC] Changes to signed char and unsigned char handling In-Reply-To: References: <20070705135402.GA4300@caradoc.them.org> X-Mailer: VM 7.19 under Emacs 22.1.50.11 X-IsSubscribed: yes Mailing-List: contact gdb-patches-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-patches-owner@sourceware.org X-SW-Source: 2007-07/txt/msg00122.txt.bz2 > > 3. Treat "char" as a character, but "unsigned char" and "signed char" > > as numbers > > Didn't RMS object to this change? He just said: Which GDB behavior is better is a matter of how often each one is convenient and how often it causes trouble. I don't know enough to have an opinion about that, but if neither one is clearly better overall, it would be best to leave GDB the way it was. mathieu lacage also said: I don't know how useful that is to you but a lot of people (the first which comes to my mind is libxml2) decided to use "unsigned char *" to identify utf-8 encoded strings in C. I don't know if this is related to the appearance of xml-builtin.c: static const char xml_feature_gdb_target_dtd[] = { '<', '!', '-', '-', ' ', 'C', 'o', 'p', 'y', 'r', 'i', 'g', 'h', 't', ' ', '(', 'C', ')', ' ', '2', ... Personally, I'm not worried by this change as my usage has a workaround. -- Nick http://www.inet.net.nz/~nickrob