public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Gabriel Dos Reis <gdr@integrable-solutions.net>
To: Mark Mitchell <mark@codesourcery.com>
Cc: Giovanni Bajo <rasky@develer.com>,
	Nathan Sidwell <nathan@codesourcery.com>,
	jason@redhat.com, gcc@gcc.gnu.org
Subject: Re: MEMBER_TYPE and CV qualifiers
Date: Mon, 18 Jul 2005 15:30:00 -0000	[thread overview]
Message-ID: <m3ll44jfoz.fsf@uniton.integrable-solutions.net> (raw)
In-Reply-To: <42DBBBB5.5090907@codesourcery.com>

Mark Mitchell <mark@codesourcery.com> writes:

| Furthermore, 9.3.1/3 is at odds with 3.9.3/1, which says:
| 
|    Each type which is  a  cv-unqualified  complete  or
|    incomplete  object  type  or  is void (_basic.types_) has three corre-
|    sponding cv-qualified versions of its type: a const-qualified version,
|    a  volatile-qualified version, and a const-volatile-qualified version.
| 
| Note that it explicitly leaves out function types.

Yes.  For some reasons (I have not gotten explanations for yet), the
specification of member functions seems to be very odd at different
places in the standard :-(

-- Gaby

  reply	other threads:[~2005-07-18 15:30 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-07-17 15:38 Nathan Sidwell
2005-07-17 20:07 ` Mark Mitchell
2005-07-18 10:15   ` Giovanni Bajo
2005-07-18 14:25     ` Mark Mitchell
2005-07-18 15:30       ` Gabriel Dos Reis [this message]
2005-07-19 18:44     ` Jason Merrill
2005-07-19 18:48       ` Mark Mitchell
2005-07-19 19:47         ` Gabriel Dos Reis
2005-07-19 20:14           ` Mark Mitchell
2005-07-19 20:35             ` Gabriel Dos Reis
2005-07-19 20:50               ` Mark Mitchell

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=m3ll44jfoz.fsf@uniton.integrable-solutions.net \
    --to=gdr@integrable-solutions.net \
    --cc=gcc@gcc.gnu.org \
    --cc=jason@redhat.com \
    --cc=mark@codesourcery.com \
    --cc=nathan@codesourcery.com \
    --cc=rasky@develer.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).