From: Bob Rossi <bob@brasko.net>
To: Stefan Burstr?m <f94sbu@efd.lth.se>
Cc: gdb@sources.redhat.com
Subject: Re: -break-list output format
Date: Thu, 20 Oct 2005 11:50:00 -0000 [thread overview]
Message-ID: <20051020114949.GA1073@white> (raw)
In-Reply-To: <344b4acc3d9.10ed0489@mail.m.bonet.se>
> Well, it includes a table header etc.If I want to build a table of the
> output in my program I would of course just parse the output and build my
> own tables with headers, labels etc.
>
> For example, -file-list-exec-source-files just lists each file in a tuple.
> But -break-list tells me the widh and height of the output etc. And I wonder
> if I need to use it or if I can just skip the table header info. Finally, I
> was just curious to know why the break-list output was done this way when
> all other commands are more 'raw' in nature.
Well, I think it's a legacy issue. The table (with headers) has been
around for a long time. Long before MI was invented. So, I'm guessing
the writer of -break-list decided it would be good to keep that
information. You can ignore it if you choose.
Bob Rossi
prev parent reply other threads:[~2005-10-20 11:50 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-07 14:23 MI parser Vladimir Prus
2005-09-07 14:29 ` Daniel Jacobowitz
2005-09-07 14:40 ` Bob Rossi
2005-10-20 11:08 ` -break-list output format Stefan Burström
2005-10-20 11:15 ` Nick Roberts
2005-10-20 11:27 ` Stefan Burström
2005-10-20 11:50 ` Bob Rossi [this message]
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=20051020114949.GA1073@white \
--to=bob@brasko.net \
--cc=f94sbu@efd.lth.se \
--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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).