From: nickrob@snap.net.nz (Nick Roberts)
To: Eli Zaretskii <eliz@gnu.org>
Cc: gdb-patches@sources.redhat.com
Subject: Re: [PATCH:doc] GDB/MI attribute names
Date: Fri, 25 Sep 2009 10:55:00 -0000 [thread overview]
Message-ID: <19132.41367.233102.480938@totara.tehura.co.nz> (raw)
In-Reply-To: <837hvnv45y.fsf@gnu.org>
> > 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?
I can't find any that don't fit the rule that I want to document. It occurred
to me that the regexp that I was using to parse MI output for Emacs wouldn't
work if certain characters, e.g "$", were used. I just want to discourage
their use in future attribute names. Parsers will have to handle existing
anomalies, if any.
> > + @var{variable} expressions should be alphabetic words or comprise of
> > + alphabetic words separated by underscores. ^^^^^^^^^^^
>
> Don't you meant "comprised of"?
Either sounds OK to me.
> 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.
No I don't really mean expression.
@var{variable} names...
would probably work.
> 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?
I'm not sure. To me, thay're not really variables but a field names (or
attribute names in HTML/XML parlance). It might mean the value rather than
the name.
How about:
@var{variable} names should be specified as a sequence of alphabetic
characters and underscores.
Or say what you would like to see. I'm not too worried about the exact
wording. I just want to formalise the output syntax a bit more.
> Btw, are digit really "verboten"? If not, replace "alphabetic" with
> "alphanumeric" above.
I've actually used the [:alnum:] character class in my parser but there are so
few names that I felt that requiring alphabetic wouldn't be restrictive.
--
Nick http://users.snap.net.nz/~nickrob
next prev parent reply other threads:[~2009-09-25 10:55 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
2009-09-25 10:55 ` Nick Roberts [this message]
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=19132.41367.233102.480938@totara.tehura.co.nz \
--to=nickrob@snap.net.nz \
--cc=eliz@gnu.org \
--cc=gdb-patches@sources.redhat.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