public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: Brendan Kehoe <brendan@zen.org> To: nobody@gcc.gnu.org Cc: gcc-prs@gcc.gnu.org Subject: Re: libstdc++/3016: stl_queue.h bugs wrt compliance Date: Thu, 31 May 2001 15:16:00 -0000 [thread overview] Message-ID: <20010531221607.3497.qmail@sourceware.cygnus.com> (raw) The following reply was made to PR libstdc++/3016; it has been noted by GNATS. From: Brendan Kehoe <brendan@zen.org> To: Phil Edwards <pedwards@disaster.jaj.com> Cc: gcc-gnats@gcc.gnu.org Subject: Re: libstdc++/3016: stl_queue.h bugs wrt compliance Date: Thu, 31 May 2001 23:16:02 +0100 >>>>> "Phil" == Phil Edwards <pedwards@disaster.jaj.com> writes: On Thu, May 31, 2001 at 09:50:54PM -0000, brendan@zen.org wrote: > *************** protected: > *** 76,81 **** > _Sequence c; > public: > ! queue() : c() {} > ! explicit queue(const _Sequence& __c) : c(__c) {} > > bool empty() const { return c.empty(); } > --- 76,80 ---- > _Sequence c; > public: > ! explicit queue(const _Sequence& __c = _Sequence()) : c(__c) {} > > bool empty() const { return c.empty(); } Phil> I disagree with removing the copy ctor. Just because it isn't Phil> mandated doesn't mean it isn't allowed. What if I wished to Phil> construct a vector-of-queue-of-T? Queue wouldn't meet the Phil> copy-constructible requirement. Hmm, I believe the copy ctor is still there, it's just now got the default argument that's required by the standard. We remove the default constructor, making queue instead set up a container if one wasn't specified by whatever is creating the queue object. B -- Brendan Kehoe brendan@zen.org http://www.zen.org/~brendan/
next reply other threads:[~2001-05-31 15:16 UTC|newest] Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top 2001-05-31 15:16 Brendan Kehoe [this message] -- strict thread matches above, loose matches on Subject: below -- 2001-06-05 8:26 Phil Edwards 2001-06-05 7:46 Gabriel Dos Reis 2001-06-05 7:46 Gabriel Dos Reis 2001-06-05 7:36 Gabriel Dos Reis 2001-05-31 15:26 Phil Edwards 2001-05-31 15:16 Phil Edwards 2001-05-31 14:56 brendan
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=20010531221607.3497.qmail@sourceware.cygnus.com \ --to=brendan@zen.org \ --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: linkBe 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).