Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Andrew Cagney <ac131313@cygnus.com>
To: Andrew Cagney <ac131313@cygnus.com>
Cc: Jim Ingham <jingham@apple.com>,
	GDB Patches <gdb-patches@sources.redhat.com>
Subject: Re: Bug with lists in tables in ui-out.c
Date: Tue, 04 Dec 2001 23:36:00 -0000	[thread overview]
Message-ID: <3C0DCE7C.4090407@cygnus.com> (raw)
In-Reply-To: <3C0DC70E.6090607@cygnus.com>

> Turns out if you have an element of a table that is a list or tuple, then
> the current ui-out table code chokes.  verify_field_alignment doesn't know
> that each of the elements of the sublist are not separate table elements, so
> it throws an error at the first one it sees.  The following patch fixes this
> bug. 

Thinking about this some more, I suspect you're constructing something like:

	table={hdr={...},body=[{{<THIS>}, ...},...}]}

or as a code sequence:

	..._body()
	  ui_out_tuple_begin(); /*row*/
	    ui_out_tupple_begin(); /* element - non-standard */
	      ui_out_field (...<THIS>..)

I'm wondering if a table is even applicable in this case.  How exactly 
should the header formatting information, for instance, be interpreted 
when there is more than one entry.

Would you have an example?

	Andrew



  reply	other threads:[~2001-12-05  7:36 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-11-28 17:42 Jim Ingham
2001-11-18 11:04 ` Jim Ingham
2001-11-29  0:20 ` Eli Zaretskii
2001-11-19 11:24   ` Eli Zaretskii
2001-12-03 13:49   ` Jim Ingham
2001-12-04  0:08     ` Eli Zaretskii
2001-12-04 23:05 ` Andrew Cagney
2001-12-04 23:36   ` Andrew Cagney [this message]
2001-12-05 11:59     ` Jim Ingham
2001-12-06 15:06       ` Andrew Cagney
2001-12-06 16:41         ` Jim Ingham
2001-12-07 11:01           ` Andrew Cagney

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=3C0DCE7C.4090407@cygnus.com \
    --to=ac131313@cygnus.com \
    --cc=gdb-patches@sources.redhat.com \
    --cc=jingham@apple.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