From: Fernando Nasser <fnasser@cygnus.com>
To: Andrew Cagney <ac131313@cygnus.com>
Cc: GDB Discussion <gdb@sources.redhat.com>
Subject: Re: GDB 5.1/mi status and question on table output
Date: Mon, 14 May 2001 12:00:00 -0000 [thread overview]
Message-ID: <3B002B28.23F0009B@cygnus.com> (raw)
In-Reply-To: <3B0010FC.3060908@cygnus.com>
Andrew Cagney wrote:
>
> FYI,
>
> The GDB/MI interface is now sitting just before the point of no return.
> I've completed all the changes that are possible without actually
> affecting the output.
>
> The task that is left is to review each of the unofficial MI commands
> and update them so that they output combinations of tuples and lists
> instead of just tuples.
>
> The first an obvious question is, what should a table look like when
> output by MI. The doco refelcts the current output, my first guess is
> to change MI so that it outputs:
>
> {
> hdr={heading, heading, ...},
> body=[{r1c1, r1c2, ...}, {r2c1, r2c2, ...}, ...]
> }
>
> Comments?
>
> There are a fixed number of columns to the table and each column has a
> name. Hence a tuple for each row and the heading.
> The number of rows, however, varies, but each one is identical, hence a
> list of rows.
>
I like the format but I have a couple of concerns:
Currently there are "headings" and "field names" and they may not be the same. I think this was done so that a GUI could be implemented fast and cope with tables that have different columns depending on certain circumstances (the breakpoint table is such a beast). I am not saying that this is the right thing, just the way it is now. The UI code using the MI currently has the option of ignoring or using the headings.
But we may change that and say that we only supply the field names and values. The problem is that we now have two ways of outputting fields: when inside a table they go without the name; when outside they go with the name.
On one hand, a more compact output without the repetition of names is appealing. On the other hand, if you have an option to get a table of breakpoints or information about a specific breakpoint, now you'll get the information about one item (breakpoint) in two different ways, depending if it came on a table (w/o field names) or as a unit (with field names).
P.S.: I am really affraid of last minute changes in the output syntax.
--
Fernando Nasser
Red Hat - Toronto E-Mail: fnasser@redhat.com
2323 Yonge Street, Suite #300
Toronto, Ontario M4P 2C9
next prev parent reply other threads:[~2001-05-14 12:00 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-05-14 10:08 Andrew Cagney
2001-05-14 12:00 ` Fernando Nasser [this message]
2001-05-14 17:48 ` Andrew Cagney
2001-05-15 6:13 ` Fernando Nasser
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=3B002B28.23F0009B@cygnus.com \
--to=fnasser@cygnus.com \
--cc=ac131313@cygnus.com \
--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