From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 22893 invoked by alias); 22 Jun 2006 20:13:16 -0000 Received: (qmail 22883 invoked by uid 22791); 22 Jun 2006 20:13:16 -0000 X-Spam-Check-By: sourceware.org Received: from nevyn.them.org (HELO nevyn.them.org) (66.93.172.17) by sourceware.org (qpsmtpd/0.31.1) with ESMTP; Thu, 22 Jun 2006 20:13:14 +0000 Received: from drow by nevyn.them.org with local (Exim 4.54) id 1FtVY8-0005mV-0t for gdb-patches@sourceware.org; Thu, 22 Jun 2006 16:13:12 -0400 Date: Thu, 22 Jun 2006 20:13:00 -0000 From: Daniel Jacobowitz To: gdb-patches@sourceware.org Subject: Re: [rfc] Implementation of qXfer Message-ID: <20060622201311.GA22171@nevyn.them.org> Mail-Followup-To: gdb-patches@sourceware.org References: <20060622033247.GA27704@nevyn.them.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.11+cvs20060403 X-IsSubscribed: yes Mailing-List: contact gdb-patches-help@sourceware.org; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-patches-owner@sourceware.org X-SW-Source: 2006-06/txt/msg00336.txt.bz2 On Thu, Jun 22, 2006 at 11:07:50PM +0300, Eli Zaretskii wrote: > They are OK, except for this issue with anchors whose names contain a > colon: this is against the Texinfo language rules. You might be lucky > with a particular Info reader, but there are others out there, and > each one of them uses a different method of searching for > cross-reference names (some use fixed strings, others use various > regular expressions). Using a colon makes them fail in different > situations and in different interesting ways. Do you have a reference for this? I spent a while with the Texinfo documentation when I was working on that, and could not find it. Just curious. > So please let's remove the colons and use some other mnemonic methods > to make the xref reflect the packet descriptor. Blech. Well, I don't know what else to use. I tried using qXfer-auxv-read, but it's pretty ugly. I can make up names for them, I suppose. I'll think about it a little longer, and then probably do that. > > [I realize they may be a bit tricky to review; the qXfer docs are large, > > and they replace the qPart docs but sit somewhere else in the alphabetical > > list of packets. > > AFAICS, you just moved the text elsewhere and replaced qPart with > qXfer, right? If there are new portions of text, please tell where > they are. No, much of the text is changed; the packet has a different format and different replies. I definitely rewrote the Reply: table and the paragraphs right after qXfer:OBJECT:read and qXfer:OBJECT:write. -- Daniel Jacobowitz CodeSourcery