Re: RFC: Formatting of type output

[Michael Elizabeth Chastain <mec@shout.net>]

Good morning Daniel,

> Does anything mechanical depend on the format of type output, besides our
> testsuite?

AFAIK, the white-space changes between v2 g++ and v3 g++ haven't
caused any external consumers of this information to break in such a way
that bug reports have reached the gnats database or the gdb mailing
lists.  So I would suspect "no".

> Does anyone have any radically strong feelings about how it
> should be formatted?

Basically no.

> Similarly, does anyone prefer to have vtbl and vbase pointers explicitly
> printed?

Are you talking about "ptype *Foo" or "print *pFoo" here?

At my day job, I use cygwin + gcc 2.95.3 + pthreads + gdb,
and the vtbl pointer is a quick indicator whether a pointer points
to a sane, live object.  That is a case of "print *pFoo".

> It seems cleaner to me to suppress them, and perhaps offer another
> way to print them explicitly.

That would be fine with me.

Michael C