From: Andrew Cagney <ac131313@redhat.com>
To: Jason Molenda <jason-swarelist@molenda.com>
Cc: gdb-patches@sources.redhat.com
Subject: Re: PATCH: Add type_sprint() function to return type in string form
Date: Wed, 23 Apr 2003 17:37:00 -0000 [thread overview]
Message-ID: <3EA6A1F8.1060502@redhat.com> (raw)
In-Reply-To: <20030423013217.A51438@molenda.com>
> Hi all, here's the follow-up patch incorporating the comments.
>
> I didn't have time to make a test case for this. I want to at least
> elicit the error message before I commit this, so I'll get something
> together tomorrow night or the night after. I don't know how easy
> it will be to add to the testsuite, but I'll at least do something
> by hand to get the error.
I assume this is in. I'm just amazed that the existing testsuite didn't
trigger this. Even a simple tweak of an existing test should do the trick.
Andrew
> 2003-04-23 Jason Molenda (jmolenda at apple dot com)
>
> * typeprint.c (type_xasprint): New function to return human-readable
> string representation of a type.
> * value.h (type_xasprint): Add prototype.
> * ada-lang.c (ada_lookup_struct_elt_type): Use type_xasprint() when
> building error message.
> * gdbtypes.c (lookup_struct_elt_type): Ditto.
> * varobj.c (varobj_get_type): Use type_xasprint() to get the type
> in a string form.
>
>
prev parent reply other threads:[~2003-04-23 14:23 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-04-18 22:24 Jason Molenda
2003-04-22 3:26 ` Daniel Jacobowitz
2003-04-22 16:48 ` Andrew Cagney
2003-04-22 16:55 ` Daniel Jacobowitz
2003-04-22 17:29 ` Andrew Cagney
2003-04-22 17:33 ` Daniel Jacobowitz
2003-04-22 19:21 ` Andrew Cagney
2003-04-22 19:28 ` Daniel Jacobowitz
2003-04-22 20:16 ` Andrew Cagney
2003-04-22 20:22 ` Daniel Jacobowitz
2003-04-22 20:35 ` Jason Molenda
2003-04-22 21:15 ` Andrew Cagney
2003-04-22 19:55 ` Kevin Buettner
2003-04-23 14:23 ` Jason Molenda
2003-04-23 17:37 ` Andrew Cagney [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=3EA6A1F8.1060502@redhat.com \
--to=ac131313@redhat.com \
--cc=gdb-patches@sources.redhat.com \
--cc=jason-swarelist@molenda.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox