public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "pcarlini at suse dot de" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug libstdc++/9679] Strange behaviour of valarray::apply method Date: Sat, 20 Mar 2004 09:27:00 -0000 [thread overview] Message-ID: <20040320092748.20871.qmail@sources.redhat.com> (raw) In-Reply-To: <20030212221600.9679.dens@stl.sarov.ru> ------- Additional Comments From pcarlini at suse dot de 2004-03-20 09:27 ------- Hi again, and thanks for the additional details. > It is clearly "Not a bug" with current C++ (either 98 or 2003 would do). Ok. > With the DR I submitted, and that would be accepted as part of C++0x, > it would become a bug in the lirbary ; but it would be a bug only > because I did not anticipate that part when making the new proposed > wording. Let me be clear: Before my proposal, the PR is invalid > because the code is ill-formed. With my proposal as currently worded, > the code would become valid (but I did not intend it to be valid). Indeed, you already pointed out this issue in your old message but I didn't fully understand it, sorry. Now, March, 2004, your DR is in the [Ready] status! Since its implications are quite important (for this PR too), first I want to document that in the sources, and point to 389. Moreover, as you often repeated in the past, [Ready] resolutions must be implemented and, for all practical purposes, must be considered part of the standard we are implementing. This means, the status of this PR, strictly speaking, right now seems to me more a plain "Open". But I fully get your point about the need for a follow up to your DR 389, so let's keep it Suspended. Could you please keep us up to date about the iter of the issue with the committee? Thanks again -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=9679
next prev parent reply other threads:[~2004-03-20 9:27 UTC|newest] Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top [not found] <20030212221600.9679.dens@stl.sarov.ru> 2003-06-02 23:50 ` reichelt@gcc.gnu.org 2003-06-02 23:53 ` reichelt@gcc.gnu.org 2004-03-19 17:06 ` pcarlini at suse dot de 2004-03-19 17:32 ` Gabriel Dos Reis 2004-03-19 17:32 ` gdr at integrable-solutions dot net 2004-03-19 18:02 ` pcarlini at suse dot de 2004-03-19 18:11 ` pcarlini at suse dot de 2004-03-19 19:12 ` gdr at integrable-solutions dot net 2004-03-20 9:27 ` pcarlini at suse dot de [this message] [not found] <bug-9679-4059@http.gcc.gnu.org/bugzilla/> 2010-02-12 0:08 ` paolo dot carlini at oracle dot com 2010-02-12 0:20 ` gdr at integrable-solutions dot net 2010-02-12 0:22 ` paolo dot carlini at oracle dot com 2010-02-12 10:43 ` paolo dot carlini at oracle dot com 2010-02-12 11:06 ` gdr at integrable-solutions dot net
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=20040320092748.20871.qmail@sources.redhat.com \ --to=gcc-bugzilla@gcc.gnu.org \ --cc=gcc-bugs@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).