[MI RFC] entryval: MI access to entry values [Re: [RFC 06/12] entryval: Display @entry parameters in bt full]

[Tom Tromey]

>>>>> "Jan" == Jan Kratochvil <jan.kratochvil@redhat.com> writes:

Jan> For (2) and (3) for FEs with proper parser an additional result
Jan> should be ignored correctly.  For FEs with some ugly manual
Jan> matching I also do not think it should be a problem as FEs are
Jan> usually used for -O0 -g code debugging while entry values are
Jan> present only in -O2 -g code.

For the record, I think we should not concern ourselves at all with such
MI consumers, if any exist.  MI has flaws, but this isn't among them; we
should expect consumers to reliably ignore new fields.

Tom