From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 6255 invoked by alias); 27 Feb 2007 12:52:05 -0000 Received: (qmail 6244 invoked by uid 22791); 27 Feb 2007 12:52:03 -0000 X-Spam-Check-By: sourceware.org Received: from nile.gnat.com (HELO nile.gnat.com) (205.232.38.5) by sourceware.org (qpsmtpd/0.31) with ESMTP; Tue, 27 Feb 2007 12:51:57 +0000 Received: from localhost (localhost [127.0.0.1]) by filtered-nile.gnat.com (Postfix) with ESMTP id 9883248D1BB; Tue, 27 Feb 2007 07:51:53 -0500 (EST) Received: from nile.gnat.com ([127.0.0.1]) by localhost (nile.gnat.com [127.0.0.1]) (amavisd-new, port 10024) with LMTP id 09954-01-4; Tue, 27 Feb 2007 07:51:53 -0500 (EST) Received: from [127.0.0.1] (nile.gnat.com [205.232.38.5]) by nile.gnat.com (Postfix) with ESMTP id E188348D17B; Tue, 27 Feb 2007 07:51:52 -0500 (EST) Message-ID: <45E42969.1030007@adacore.com> Date: Tue, 27 Feb 2007 17:06:00 -0000 From: Robert Dewar User-Agent: Thunderbird 1.5.0.9 (Windows/20061207) MIME-Version: 1.0 To: Nick Roberts CC: Daniel Jacobowitz , Jan Kratochvil , mathieu lacage , gdb@sourceware.org Subject: Re: [RFC] Signed/unsigned character arrays are not strings References: <17887.62990.937672.281975@kahikatea.snap.net.nz> <20070224161315.GA27534@caradoc.them.org> <17888.39894.136355.447008@kahikatea.snap.net.nz> <1172390381.2584.18.camel@mathieu> <20070225195350.GA12811@host0.dyn.jankratochvil.net> <20070226004457.GA9926@caradoc.them.org> <17892.4014.160191.285423@kahikatea.snap.net.nz> In-Reply-To: <17892.4014.160191.285423@kahikatea.snap.net.nz> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-IsSubscribed: yes Mailing-List: contact gdb-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-owner@sourceware.org X-SW-Source: 2007-02/txt/msg00271.txt.bz2 Nick Roberts wrote: > That answers the question that we are really asking and justifies the patch. Not necessarily. First it is only a claim, without documentation, second, any incompatible change seems basically problematic. I prefer to avoid this incompatible change, it seems like it would be a surprise to a substantial number of users. For sure the use of unsigned char for character data is pretty common. > > > We can document how to produce string output more > > clearly in the manual, perhaps? I would instead document more clearly how to produce the integer output.