From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 7563 invoked by alias); 23 Jun 2006 07:34:53 -0000 Received: (qmail 7547 invoked by uid 22791); 23 Jun 2006 07:34:52 -0000 X-Spam-Check-By: sourceware.org Received: from nitzan.inter.net.il (HELO nitzan.inter.net.il) (192.114.186.20) by sourceware.org (qpsmtpd/0.31) with ESMTP; Fri, 23 Jun 2006 07:34:50 +0000 Received: from HOME-C4E4A596F7 (IGLD-84-228-239-250.inter.net.il [84.228.239.250]) by nitzan.inter.net.il (MOS 3.7.3-GA) with ESMTP id DVM39082 (AUTH halo1); Fri, 23 Jun 2006 10:34:46 +0300 (IDT) Date: Fri, 23 Jun 2006 07:34:00 -0000 Message-Id: From: Eli Zaretskii To: gdb-patches@sourceware.org In-reply-to: <20060622201311.GA22171@nevyn.them.org> (message from Daniel Jacobowitz on Thu, 22 Jun 2006 16:13:11 -0400) Subject: Re: [rfc] Implementation of qXfer Reply-to: Eli Zaretskii References: <20060622033247.GA27704@nevyn.them.org> <20060622201311.GA22171@nevyn.them.org> 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/msg00353.txt.bz2 > Date: Thu, 22 Jun 2006 16:13:11 -0400 > From: Daniel Jacobowitz > > 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. The Texinfo manual doesn't say that explicitly for anchors. It does say that for node names: * Unfortunately, you cannot use periods, commas, colons or parentheses within a node name; these confuse the Texinfo processors. These limitations are due to the syntax of menus and cross-references where these characters delimit syntactically significant parts of the reference. In the section about anchors, there's this text that hints that anchors and nodes share the same limitations: Anchor names and node names may not conflict. Anchors and nodes are given similar treatment in some ways; for example, the `goto-node' command in standalone Info takes either an anchor name or a node name as an argument. I will ask the Texinfo maintainer to add an explicit text about anchor name limitations. > > 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. How about "qXfer auxv read" or "qXfer read auxiliary vector"? > > 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. Well, at least in this hunk the text was not touched: > -Fields within the packet should be separated using @samp{,} @samp{;} or > @cindex remote protocol, field separator > +Fields within the packet should be separated using @samp{,} @samp{;} or > @samp{:}. Except where otherwise noted all numbers are represented in > @sc{hex} with leading zeros suppressed. There are several commas missing in these two sentences. Anyway, I've read all of your text yesterday, so it's okay with me.