From: Daniel Jacobowitz <drow@false.org>
To: Jim Blandy <jimb@red-bean.com>
Cc: gdb@sources.redhat.com
Subject: Re: Letters reserved for future use
Date: Tue, 15 Nov 2005 04:36:00 -0000 [thread overview]
Message-ID: <20051115043603.GB12583@nevyn.them.org> (raw)
In-Reply-To: <8f2776cb0511141706n692c7d51j1ffa959bf1961948@mail.gmail.com>
On Mon, Nov 14, 2005 at 05:06:32PM -0800, Jim Blandy wrote:
> In (gdb)Remote Serial Protocol, every upper- and lower-case letter
> that is not given a meaning is marked individually as "reserved for
> future use". This is kind of dopey. Could we just have one remark at
> the top that says that all upper- and lower-case letters not defined
> there are reserved for future use?
What Eli said :-)
> What should people looking to make vendor-specific extensions to the
> protocol do? Are they required to stay within the general query /
> general set commands, with a vendor prefix?
That's what I've done in the past. Well, I've also done a certain
amount of just Making Stuff Up, but that's not what I recommend when
people ask me :-)
A reserved "long command" prefix that isn't in the query namespace
might help aesthetically, but would offer no technical value.
--
Daniel Jacobowitz
CodeSourcery, LLC
next prev parent reply other threads:[~2005-11-15 4:36 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-15 1:06 Jim Blandy
2005-11-15 4:08 ` Eli Zaretskii
2005-11-15 4:36 ` Daniel Jacobowitz [this message]
2005-11-15 9:09 ` Jim Blandy
2005-11-17 4:13 ` Daniel Jacobowitz
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=20051115043603.GB12583@nevyn.them.org \
--to=drow@false.org \
--cc=gdb@sources.redhat.com \
--cc=jimb@red-bean.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