Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Nick Roberts <nickrob@snap.net.nz>
To: Eli Zaretskii <eliz@gnu.org>
Cc: gdb@sources.redhat.com
Subject: Re: -var-show-attributes response syntax
Date: Fri, 10 Nov 2006 23:33:00 -0000	[thread overview]
Message-ID: <17749.2926.508338.599064@kahikatea.snap.net.nz> (raw)
In-Reply-To: <u8xiikieg.fsf@gnu.org>

 > Sorry, I no longer understand the problem you were talking about.
 > AFAICS, the `{}' are literal (and so don't need to be discussed),
 > while `|' is _not_ a literal character and is already documented in
 > "Notation and Terminology".  What am I missing?

From "GDB/MI Variable Objects" in the manual:

      lang=LANG-SPEC,exp=EXPRESSION

  where LANG-SPEC is `{"C" | "C++" | "Java"}'.

means e.g lang="C" not lang={"C"}

      status=ATTR [ ( ,ATTR )* ]

  where ATTR is `{ { editable | noneditable } | TBD }'.

means e.g attr="editable" not attr={{"editable"}}

As Andreas says, status=ATTR should be attr=ATTR.  Also editable | noneditable
should presumably be strings:

  where ATTR is `{ { "editable" | "noneditable" } | TBD }'.

Having said that I always find it hard to use one syntax to describe another
in an unambiguous way and it's not that hard to find out what is meant by
invoking GDB with MI.


-- 
Nick                                           http://www.inet.net.nz/~nickrob


  reply	other threads:[~2006-11-10 23:33 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-11-10 13:55 Vladimir Prus
2006-11-10 16:34 ` Nick Roberts
2006-11-10 16:53   ` Vladimir Prus
2006-11-10 20:47     ` Nick Roberts
2006-11-10 21:06       ` Vladimir Prus
2006-11-10 21:23         ` Nick Roberts
2006-11-10 17:02   ` Andreas Schwab
2006-11-10 21:46   ` Eli Zaretskii
2006-11-10 21:54     ` Nick Roberts
2006-11-10 23:10       ` Eli Zaretskii
2006-11-10 23:33         ` Nick Roberts [this message]
2006-11-11  9:26           ` Eli Zaretskii
2006-11-11 10:03             ` Nick Roberts

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=17749.2926.508338.599064@kahikatea.snap.net.nz \
    --to=nickrob@snap.net.nz \
    --cc=eliz@gnu.org \
    --cc=gdb@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