This is the mail archive of the mailing list for the GDB project.

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: [rfc] Implementation of qXfer

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

> 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

> > [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

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]