Re: [PATCH 8/9] class-local typedef substitutions

[Tom Tromey <tromey@redhat.com>]

>>>>> "Pedro" == Pedro Alves <palves@redhat.com> writes:

Tom> More testing revealed an oddity in this code (a latent bug exposed by
Tom> the subsequent Python patch); and the fix I chose required some changes
Tom> to some MI test cases as well.  The particular change was that
Tom> previously gdb could emit "long int" but now it will emit just "long" --
Tom> I consider this to be an ok (perhaps even preferable) change.

Pedro> I'm confused and curious at why such a change would be necessary.  I
Pedro> couldn't find it from a quick look over the patch.
Pedro> Can you expand a little?  Does this also affect the CLI?

It has been a while, but I think the difference depends on whether the
type name is sent through canonicalization or not.

Pedro> Why expect both long and "long int"?  Is this compiler / debug format
Pedro> dependent, perhaps?

I will take another look and figure it out.

Tom