public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: Phil Edwards <pedwards@disaster.jaj.com> To: nobody@gcc.gnu.org Cc: gcc-prs@gcc.gnu.org Subject: Re: libstdc++/3036: pair constructor not updated per DR 265 Date: Sun, 03 Jun 2001 18:26:00 -0000 [thread overview] Message-ID: <20010604012601.11822.qmail@sourceware.cygnus.com> (raw) The following reply was made to PR libstdc++/3036; it has been noted by GNATS. From: Phil Edwards <pedwards@disaster.jaj.com> To: kenny.simpson@gs.com Cc: gcc-gnats@gcc.gnu.org, theonetruekenny@yahoo.com Subject: Re: libstdc++/3036: pair constructor not updated per DR 265 Date: Sun, 3 Jun 2001 20:04:02 -0400 On Sat, Jun 02, 2001 at 01:04:16AM -0000, kenny.simpson@gs.com wrote: > The constructor for pair has been changed, see: > http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-defects.html#265 The notes on that DR mention that "this is the right thing to do now that core issue 178 has cleared it up." Does gcc DTRT as far as 178 goes? It seems to be introducing the "value-initialized" thing, and I'd hate to introduce a fix in the library which depends on a change in the compiler which hasn't happened yet. Maybe gcc has been behaving correctly already, and they're just fixing up the wording in the standard text. In which case my question is utterly moot. -- pedwards at disaster dot jaj dot com | pme at sources dot redhat dot com devphil at several other less interesting addresses in various dot domains The gods do not protect fools. Fools are protected by more capable fools.
next reply other threads:[~2001-06-03 18:26 UTC|newest] Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top 2001-06-03 18:26 Phil Edwards [this message] -- strict thread matches above, loose matches on Subject: below -- 2001-06-03 23:26 Kenny Simpson 2001-06-01 18:06 kenny.simpson
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=20010604012601.11822.qmail@sourceware.cygnus.com \ --to=pedwards@disaster.jaj.com \ --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).