This is the mail archive of the gdb-patches@sourceware.org mailing list for the GDB project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: [RFC - Python Scripting] New method gdb.Architecture.disassemble


On Wed, Feb 6, 2013 at 3:57 PM, André Pönitz
<andre.poenitz@mathematik.tu-chemnitz.de> wrote:
>> 1. [1, 2, 3]
>> 2. ['a' : 1, 'b': 2, 'c': 3]
>> 3. ['a': 1, 'a': 2, 'a': 3]
>>
>> 1 and 2 can be encapsulated with fundamental Python data structures. I
>> am not aware of any fundamental Python data structure which can
>> capture 3.
>
> Are you asking whether you need to create 3. or whether you need to
> be able to read it?
>
> I think _producing_ 3. is never really needed from a consumers point
> of view, but happens more or less accidentally for historic reason.
> So the consumer has to be aware of the possibility of it appearing
> but generally handles it similarly to 1.
>
> New commands on the producer side could restrict themselves to not
> producing 3, i.e. to use "normal" Python structures only.

Python ui_out is a way to get what a "producer" produces into Python.
Hence, as Matt and Tom say, we want to be able to entertain as large a
set of producers as possible. At least, that is what I understand from
their comments.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]