Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: David Carlton <carlton@math.stanford.edu>
To: Daniel Jacobowitz <drow@mvista.com>
Cc: gdb-patches@sources.redhat.com
Subject: Re: [rfa] handle integer downsizing correctly in C++ overloading
Date: Tue, 04 Feb 2003 21:23:00 -0000	[thread overview]
Message-ID: <ro13cn34u5h.fsf@jackfruit.Stanford.EDU> (raw)
In-Reply-To: <20030204183222.GB22089@nevyn.them.org>

On Tue, 4 Feb 2003 13:32:22 -0500, Daniel Jacobowitz <drow@mvista.com> said:

> I (still) don't have a copy of the standard; I think I'll see about
> getting one this week.  However, your explanation makes sense, and
> matches my reading of the conversion code that GCC uses for overload
> resolution (gcc/cp/call.c:build_conv and standard_conversion).  This
> patch is OK.

Thanks, committed.  To be honest, I would be shocked if we were
getting conversion completely correct even after this patch (even
setting aside scope issues arising from namespaces, subclasses, using
declarations, and the like), but it's an improvement.  I've read the
relevant section of the standard only enough to know that:

* Narrowing integer conversions are definitely acceptable, albeit not
  optimal.

* Anybody who can figure out how overloading and namespaces should
  interact based on what the standard says is a _lot_ better at
  reading standards than I am.

In cases like this, I've started adding code to the .cc files in the
testsuite to verify that the compiler and I agree with what the
standard says, because I don't always trust my understanding of these
issues.

David Carlton
carlton@math.stanford.edu


      reply	other threads:[~2003-02-04 21:23 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-01-31 19:57 David Carlton
2003-01-31 20:04 ` David Carlton
2003-02-04 19:10 ` Daniel Jacobowitz
2003-02-04 21:23   ` David Carlton [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=ro13cn34u5h.fsf@jackfruit.Stanford.EDU \
    --to=carlton@math.stanford.edu \
    --cc=drow@mvista.com \
    --cc=gdb-patches@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