From: Eli Zaretskii <eliz@gnu.org>
To: nickrob@snap.net.nz (Nick Roberts)
Cc: gdb-patches@sources.redhat.com
Subject: Re: [PATCH:doc] GDB/MI attribute names
Date: Fri, 25 Sep 2009 08:09:00 -0000 [thread overview]
Message-ID: <837hvnv45y.fsf@gnu.org> (raw)
In-Reply-To: <19131.17428.428101.481874@totara.tehura.co.nz>
> Date: Thu, 24 Sep 2009 22:04:04 +1200
> From: nickrob@snap.net.nz (Nick Roberts)
>
> This patch, slightly paranoid, document the current practice for attribute
> names. I don't want future names to break exiting parsers.
I agree, assuming that what you wrote is factually correct at this
point, and that we have no good reasons to modify it VSN. Is that
indeed so?
> + @var{variable} expressions should be alphabetic words or comprise of
> + alphabetic words separated by underscores. ^^^^^^^^^^^
Don't you meant "comprised of"?
In any case, the text you suggests sounds a bit inaccurate to me.
(Maybe I just don't know enough about MI, so please bear with me.)
You say "variable expressions", but an expression can use operators,
can't it? If it can, then the operators are not generally alphabetic
characters.
Based on my understanding of what you meant, I suggest to rephrase as
follows:
Every @var{variable} should be specified as a sequence of alphabetic
characters and underscores.
Does that reflect correctly what you wanted to say?
Btw, are digit really "verboten"? If not, replace "alphabetic" with
"alphanumeric" above.
Thanks.
next prev parent reply other threads:[~2009-09-25 8:09 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-24 10:04 Nick Roberts
2009-09-25 8:09 ` Eli Zaretskii [this message]
2009-09-25 10:55 ` Nick Roberts
2009-09-25 11:09 ` Vladimir Prus
2009-09-25 12:34 ` Nick Roberts
2009-09-25 12:53 ` Vladimir Prus
2009-09-25 13:19 ` Eli Zaretskii
2009-09-25 13:35 ` Vladimir Prus
2009-09-25 13:59 ` Eli Zaretskii
2009-09-25 14:15 ` Vladimir Prus
2009-09-25 15:54 ` Eli Zaretskii
2009-09-25 22:32 ` Nick Roberts
2009-09-25 23:12 ` Nick Roberts
2009-09-28 16:25 ` Vladimir Prus
2009-09-26 9:00 ` Eli Zaretskii
2009-09-25 13:13 ` Eli Zaretskii
2009-09-25 13:40 ` Vladimir Prus
2009-09-25 13:07 ` 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=837hvnv45y.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=gdb-patches@sources.redhat.com \
--cc=nickrob@snap.net.nz \
/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