public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: "Artem Khodush" <artem@duma.gov.ru>
To: nobody@gcc.gnu.org
Cc: gcc-prs@gcc.gnu.org
Subject: Re: c++/3402: GCC 3.0 does not compile using push_back function on a vector of pairs of const strings
Date: Tue, 26 Jun 2001 01:06:00 -0000	[thread overview]
Message-ID: <20010626080601.2740.qmail@sourceware.cygnus.com> (raw)

The following reply was made to PR c++/3402; it has been noted by GNATS.

From: "Artem Khodush" <artem@duma.gov.ru>
To: <roy@haematic.org>
Cc: <gcc-gnats@gcc.gnu.org>, <gcc-bugs@gcc.gnu.org>
Subject: Re: c++/3402: GCC 3.0 does not compile using push_back function on a vector of pairs of const strings
Date: Tue, 26 Jun 2001 11:48:49 +0400

 > GCC 3.0 does not compile using push_back function on a vector of pairs of const strings
 
 GCC 3.0 is right, the c++ standard states it pretty clear: anything const 
 can not be stored in any kind of standard containers.
 
   23.1  Container requirements              
 ...
 3 The  type of objects stored in these components must meet the require-
   ments of CopyConstructible types  (_lib.copyconstructible_),  and  the
   additional requirements of Assignable types.
 
 4 In  Table  2,  T is the type used to instantiate the container, t is a
   value of T, and u is a value of (possibly const) T.
 
                      Table 2--Assignable requirements
 
 
             +------------------------------------------------+
             |expression   return type      post-condition    |
             +------------------------------------------------+
             |t = u        T&            t is equivalent to u |
             +------------------------------------------------+
 
 
 


             reply	other threads:[~2001-06-26  1:06 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-06-26  1:06 Artem Khodush [this message]
  -- strict thread matches above, loose matches on Subject: below --
2001-06-26  5:25 lerdsuwa
2001-06-25  5:06 roy

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=20010626080601.2740.qmail@sourceware.cygnus.com \
    --to=artem@duma.gov.ru \
    --cc=gcc-prs@gcc.gnu.org \
    --cc=nobody@gcc.gnu.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).