From: Keith Seitz <keiths@redhat.com>
To: Tom Tromey <tromey@redhat.com>
Cc: "gdb-patches@sourceware.org ml" <gdb-patches@sourceware.org>
Subject: Re: [RFA] c++/13225
Date: Tue, 11 Oct 2011 19:44:00 -0000 [thread overview]
Message-ID: <4E949C94.4000004@redhat.com> (raw)
In-Reply-To: <m3mxd78gnh.fsf@fleche.redhat.com>
On 10/11/2011 12:36 PM, Tom Tromey wrote:
>>>>>> "Keith" == Keith Seitz<keiths@redhat.com> writes:
> Sami updated overloading resolution to more faithfully follow the C++
> spec. So, I think it would be useful to justify this patch in terms of
> the standard.
Other than the "0" case (which shouldn't elicit a warning (but will)), I
cannot justify allowing int -> pointer conversion via the standard. I
was simply thinking of the (non-stupid) user who wanted (more
generically) to do:
(gdb) print my_function (0x1234578)
That *would* require a cast, but I cannot convince myself that gdb need
be so strict. Issue a warning about a non-standard conversion and do it.
"0" is, of course, a special case for pointer conversion. The standard
explicitly allows that (4.10.1 in n3290 draft).
Let me know what you would like me to do.
Keith
next prev parent reply other threads:[~2011-10-11 19:44 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-11 19:16 Keith Seitz
2011-10-11 19:36 ` Tom Tromey
2011-10-11 19:44 ` Keith Seitz [this message]
2011-10-12 13:40 ` Tom Tromey
2011-10-13 16:07 ` Keith Seitz
2011-10-14 19:35 ` Tom Tromey
2011-10-14 20:26 ` Keith Seitz
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=4E949C94.4000004@redhat.com \
--to=keiths@redhat.com \
--cc=gdb-patches@sourceware.org \
--cc=tromey@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