From: Daniel Jacobowitz <drow@false.org>
To: Nathan Sidwell <nathan@codesourcery.com>
Cc: gdb-patches@sourceware.org
Subject: Re: RFC: Remote "qSupported" features probe
Date: Tue, 13 Jun 2006 13:44:00 -0000 [thread overview]
Message-ID: <20060613134414.GA6112@nevyn.them.org> (raw)
In-Reply-To: <448EBF9C.6020509@codesourcery.com>
On Tue, Jun 13, 2006 at 02:37:32PM +0100, Nathan Sidwell wrote:
> Daniel,
>
> is there a reason that the qSupported uses a ':' as the first separator but
> ';' for subsequent separators? It seems needlessly different.
I agree. But, that's what Jim added to the top of General Query Packets
as the convention:
The name of a query or set packet should be separated from any
parameters by a `:'; the parameters themselves should be separated by
`,' or `;'. Stubs must be careful to match the full packet name, and
check for a separator or the end of the packet, in case two packet
names share a common prefix. New packets should not begin with `qC',
`qP', or `qL'(1).
I don't feel too strongly about it. Do you think it should be changed?
--
Daniel Jacobowitz
CodeSourcery
next prev parent reply other threads:[~2006-06-13 13:44 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-12 19:53 Daniel Jacobowitz
2006-06-13 8:43 ` Nathan Sidwell
2006-06-13 13:07 ` Daniel Jacobowitz
2006-06-13 18:41 ` Eli Zaretskii
2006-06-13 18:43 ` Daniel Jacobowitz
2006-06-20 20:51 ` Daniel Jacobowitz
2006-06-21 3:14 ` Eli Zaretskii
2006-06-21 14:44 ` Daniel Jacobowitz
2006-06-13 13:38 ` Nathan Sidwell
2006-06-13 13:44 ` Daniel Jacobowitz [this message]
2006-06-13 13:46 ` Nathan Sidwell
2006-06-13 18:23 ` Eli Zaretskii
2006-06-13 18:35 ` Daniel Jacobowitz
2006-06-13 18:45 ` Eli Zaretskii
2006-06-13 19:16 ` Daniel Jacobowitz
2006-06-14 3:26 ` Eli Zaretskii
2006-06-20 20:42 ` Daniel Jacobowitz
2006-06-21 3:11 ` Eli Zaretskii
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20060613134414.GA6112@nevyn.them.org \
--to=drow@false.org \
--cc=gdb-patches@sourceware.org \
--cc=nathan@codesourcery.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox