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

[Tom Tromey <tromey@redhat.com>]

>>>>> "Tom" == Tom Tromey <tromey@redhat.com> writes:

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?

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

Yes, it is due to C++ name canonicalization.

It may be possible to avoid this in some cases, but I can't think of a
situation where the current approach would make the output worse.

It does affect the CLI in some cases, but I see now that I missed the
'default' case in c_type_print_base.  I will update that and see what
happens.

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

Tom> I will take another look and figure it out.

I think it is safe to just expect "long".
I'll change the patch.

Tom