From: Vladimir Prus <ghost@cs.msu.su>
To: gdb@sources.redhat.com
Subject: Re: Formatting of function pointer value
Date: Mon, 11 Jul 2005 07:11:00 -0000 [thread overview]
Message-ID: <dat60d$nu$1@sea.gmane.org> (raw)
In-Reply-To: <dat0lm$kuh$4@sea.gmane.org>
Vladimir Prus wrote:
> Daniel Jacobowitz wrote:
>
>> On Fri, Jul 08, 2005 at 12:50:48PM +0400, Vladimir Prus wrote:
>>> Vladimir Prus wrote:
>>>
>>>
>>> > the value of *p3 is printed like this:
>>> >
>>> > (gdb) print *p3
>>> > $1 = {int (int)} 0xb7ee6e9c <__DTOR_END__+4>
>>>
>>> Even more strange is this:
>>>
>>> (gdb) print p3
>>> $2 = (int (*)(int)) 0xb7ee6e9c <__DTOR_END__+4>
>>> (gdb) print *p3
>>> $3 = {int (int)} 0xb7ee6e9c <__DTOR_END__+4>
>>>
>>> Why does formatting of the type different in the second case, and uses
>>> braces instead of parenthesis?
>>
>> One is a pointer to function, the other is a function.
>
> I'm sorry, I don't understand this. Is human user supposed to know that
> '{' starts a function? What harm will it make if parenthesis are used in
> both cases?
BTW, the code in question says:
/* 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, "} ");
Is "FIXME" still relevant?
- Volodya
next prev parent reply other threads:[~2005-07-11 7:11 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-07-08 8:02 Vladimir Prus
2005-07-08 8:51 ` Vladimir Prus
2005-07-08 13:59 ` Daniel Jacobowitz
2005-07-11 5:40 ` Vladimir Prus
2005-07-11 7:11 ` Vladimir Prus [this message]
2005-07-11 8:35 ` Andreas Schwab
2005-07-11 13:03 ` Daniel Jacobowitz
2005-07-08 13:58 ` Daniel Jacobowitz
2005-07-11 5:38 ` Vladimir Prus
2005-07-11 7:06 ` Nick Roberts
2005-07-11 7:21 ` Vladimir Prus
2005-07-11 7:42 ` Vladimir Prus
2005-07-11 13:08 ` Daniel Jacobowitz
2005-07-11 13:21 ` Vladimir Prus
2005-07-11 13:27 ` Daniel Jacobowitz
2005-07-14 8:10 ` Vladimir Prus
2005-07-11 8:08 ` Nick Roberts
2005-07-11 9:05 ` Vladimir Prus
2005-07-11 9:53 ` Nick Roberts
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='dat60d$nu$1@sea.gmane.org' \
--to=ghost@cs.msu.su \
--cc=gdb@sources.redhat.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