This is the mail archive of the
gdb-patches@sourceware.org
mailing list for the GDB project.
Re: py uiout was: Re: [PATCH 3/3] PR gdb/13860: don't lose '-interpreter-exec console EXECUTION_COMMAND''s output in async mode.
- From: Tom Tromey <tromey at redhat dot com>
- To: Matt Rice <ratmice at gmail dot com>
- Cc: Pedro Alves <palves at redhat dot com>, Yao Qi <yao at codesourcery dot com>, gdb-patches at sourceware dot org
- Date: Fri, 18 May 2012 11:05:16 -0600
- Subject: Re: py uiout was: Re: [PATCH 3/3] PR gdb/13860: don't lose '-interpreter-exec console EXECUTION_COMMAND''s output in async mode.
- References: <CACTLOFrLVotJsBNsB5L7tZEknv29oQbEZ-TJcs_O1erBRvuxBQ@mail.gmail.com>
>>>>> "Matt" == Matt Rice <ratmice@gmail.com> writes:
Matt> FWIW the attachments to PR 11688 should probably be able to see if
Matt> this is an issue (I would also imagine it seems like it would)
Matt> the main issue is that the current ui-out types do not contain
Matt> adequate information to allow one to pre-allocate a python object of
Matt> e.g. a dictionary or a list, instead we must wait after starting the
Matt> list or dictionary until the first item is added to know if it is
Matt> key/value or merely values,
Could you walk me through it?
I am still having trouble understanding the issue.
It seems to me that ui-out tables would map to a list of objects; and
lists or tuples would generally map to lists, except if they are a
direct child of a table.
Tom