From: Nick Roberts <nickrob@snap.net.nz>
To: Vladimir Prus <ghost@cs.msu.su>
Cc: gdb-patches@sources.redhat.com
Subject: Re: Remove type prefix for -var-evaluate-expression/functions
Date: Fri, 17 Mar 2006 10:20:00 -0000 [thread overview]
Message-ID: <17434.29587.870198.135084@kahikatea.snap.net.nz> (raw)
> Hi,
> the following patch removes 'type prefix' from output of
> -var-evaluate-expression applied to objects of function type (not pointers
> to functions, but functions).
>
> It causes no regression in the testsuite for me.
But I guess a new test would help prevent a regression (in the code) in the
future.
> Changelog:
>
> 2006-03-15 Vladimir Prus <ghost@cs.msu.su>
>
> * c-valprint.c
> (c_val_print): Don't print type prefix for functions.
> (c_value_print): Print type prefix for functions here.
> Patch attached.
...
> + if (TYPE_CODE (type) == TYPE_CODE_FUNC)
This condition must always be true here (case TYPE_CODE_FUNC:).
> + {
> + /* FIXME, we should consider, at least for ANSI C language, eliminating
> + the distinction made between FUNCs and POINTERs to FUNCs. */
> + fprintf_filtered (stream, "{");
> + type_print (type, "", stream, -1);
> + fprintf_filtered (stream, "} ");
> + }
> +
> +
> if (objectprint && (TYPE_CODE (type) == TYPE_CODE_CLASS))
> {
> /* Attempt to determine real type of object */
Where's the patch for c_value_print?
--
Nick http://www.inet.net.nz/~nickrob
PS As Jason Molenda suggested to me, if you put "diff -p" in your it will
add the name of the function at the top of each hunk which makes it easier
for others to read.
next reply other threads:[~2006-03-17 8:31 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-17 10:20 Nick Roberts [this message]
2006-03-17 10:42 ` Vladimir Prus
-- strict thread matches above, loose matches on Subject: below --
2006-03-17 14:33 Nick Roberts
2006-03-17 15:03 ` Vladimir Prus
2006-03-18 1:26 ` Daniel Jacobowitz
2006-04-04 7:18 ` Vladimir Prus
2006-05-05 20:47 ` Daniel Jacobowitz
2006-03-15 16:27 Vladimir Prus
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=17434.29587.870198.135084@kahikatea.snap.net.nz \
--to=nickrob@snap.net.nz \
--cc=gdb-patches@sources.redhat.com \
--cc=ghost@cs.msu.su \
/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