Re: RFA: unbreak typedefed bitfield

Tom Tromey
2009-12-18T19:55:17Z

>>>>> "Joel" == Joel Brobecker <brobecker@adacore.com> writes:

Joel> I have a general feeling that most of the time, the typedef should
Joel> have never been passed down. But I haven't spent the time and
Joel> effort to try to think globally.

There are definitely cases where we want to preserve the type that the
user wrote.

In C, this matters for printing various character types. E.g., both
wchar_t and char32_t may be typedefs of int, but we want to print them
differently if they use different encodings.

This preservation has to be pervasive, because of things like:

print (wchar_t) 32

This example doesn't work today, but probably should.

I agree that check_typedef is a problem.

Perhaps we could approach the check_typedef problem using a semantic
analyzer to ensure correct use. There are other idioms in gdb that also
require careful attention that would benefit from this; cleanups and
proper use of TRY_CATCH come to mind, but there are probably others.

Another approach would be to change TYPE_LENGTH to first call
check_typedef.

Tom