From: Paul Hilfinger <Hilfinger@adacore.com>
To: gdb@sourceware.org
Subject: Strange case for expect_type
Date: Wed, 28 Nov 2007 08:45:00 -0000 [thread overview]
Message-ID: <20071128084549.E25BD48CC02@nile.gnat.com> (raw)
Can anyone explain this code fragment from evaluate_subexp_standard?
case UNOP_IND:
if (expect_type && TYPE_CODE (expect_type) == TYPE_CODE_PTR)
expect_type = TYPE_TARGET_TYPE (check_typedef (expect_type));
arg1 = evaluate_subexp (expect_type, exp, pos, noside);
It SEEMS to be saying that if I "expect" type T* from expression *E, then
I should expect type T from E. Say what? Thanks for any help.
Paul Hilfinger
next reply other threads:[~2007-11-28 8:45 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-28 8:45 Paul Hilfinger [this message]
2007-11-28 13:07 ` Daniel Jacobowitz
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=20071128084549.E25BD48CC02@nile.gnat.com \
--to=hilfinger@adacore.com \
--cc=gdb@sourceware.org \
/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