Re: [RFA 1/5] Remove some ui_out-related cleanups from Python

[Pedro Alves <palves@redhat.com>]

On 02/09/2017 12:48 PM, Pedro Alves wrote:
> Hi Matt,
> 
> On 02/09/2017 04:34 AM, Matt Rice wrote:
> 
>> Wondering if this would be a good opportunity to try and transition
>> ui_out_list construction into a more type safe manner, e.g.
>> result ==> variable "=" value
>> list ==> "[]" | "[" value ( "," value )* "]" | "[" result ( "," result )* "]"
>>
>> currently when building a list, it didn't specify whether you were
>> declaring a list of results or a list of values, unless/until the
>> first value or result was added, and IIRC this | property wasn't
>> really explicitly enforced.
> 
> More type-safety sounds good to me.  :-)
> 
> Can you give an example of a command that outputs a result list,
> and an example of a command that outputs a value list?
> 
>> it'd be nice to migrate this to something like:
>> result_list, value_list, deprecated_unspecified_list, It would be nice
>> to know if/when you guys think it would be a convenient time to
>> introduce such a change so I could get back up to speed...
> 
> Simon has already C++-fyed ui_out in master, so this seems like
> a good time to me.

Though, to be clear, IIUC, you're talking about changing
GDB internals without affecting the resulting MI output, right?

Thanks,
Pedro Alves