This is the mail archive of the
gdb-patches@sourceware.org
mailing list for the GDB project.
Re: [RFC] Simplify varobj type printing
- From: Tom Tromey <tromey at redhat dot com>
- To: Vladimir Prus <vladimir at codesourcery dot com>
- Cc: gdb-patches at sources dot redhat dot com
- Date: Mon, 29 Jun 2009 09:44:53 -0600
- Subject: Re: [RFC] Simplify varobj type printing
- References: <200906291627.11627.vladimir@codesourcery.com>
- Reply-to: tromey at redhat dot com
>>>>> "Vladimir" == Vladimir Prus <vladimir@codesourcery.com> writes:
Vladimir> 1. Why the current code works this way. It appears to
Vladimir> be like this since initial commit in 2000, and I don't
Vladimir> see any reason why creating value_zero and then taking its
Vladimir> type is gonna change anything.
I have no idea. This seems very weird to me. In the Python API we do
it the more obvious way and we haven't heard any complaints. See
python-type.c:typy_str.
Vladimir> 2. Is there no way, outside MI code, to get char* representation
Vladimir> of a type? If so, shall I add a function to typeprint.h?
That would be fine by me; I would use gdbtypes.h, because typeprint.h
seems both dead-ish and like something only used by language
implementations of type printing.
Tom