public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "redi at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/48940] GCC fails to issue expected error
Date: Tue, 10 May 2011 10:18:00 -0000	[thread overview]
Message-ID: <bug-48940-4-OjnzfpGbuL@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-48940-4@http.gcc.gnu.org/bugzilla/>

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=48940

--- Comment #4 from Jonathan Wakely <redi at gcc dot gnu.org> 2011-05-10 10:07:53 UTC ---
(In reply to comment #2)
> Sorry to be cryptic as to the part of the standard I was talking about.  Yes, I
> was referring to report 391/589.
> 
> Yes, I agree that g++ should not issue an error for this file running in C++03
> mode.

(I assume you mean C++0x here)

DR 391 was resolved in 2005 and G++'s behaviour was changed intentionally, see
PR 25950

> What I am filing a bug about is that g++ used to issue an error running in
> C++98 mode, and now g++ does not issue an error running in C++98 mode.  I claim
> that it should issue an error, because I understood issue the defect reports
> only to affect the C++03 standardization.  Is this correct?

Technically yes, but the intent of the committee is that it should work, and
implementing that is more useful for users.  Does it actually serve any
advantage to reject the code, other than strict conformance?  With extended
SFINAE in C++0x you could make use of it, but the code is valid in C++0x, and
extended SFINAE isn't part of C++98.

There are lots of DRs that G++ implements, counter to the exact wording in
C++98 or C++03.

Jason, as the author of the fix for PR 25950, do you have an opinion?


  parent reply	other threads:[~2011-05-10 10:18 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-05-10  2:00 [Bug c++/48940] New: " vanceza at gmail dot com
2011-05-10  9:27 ` [Bug c++/48940] " redi at gcc dot gnu.org
2011-05-10  9:52 ` vanceza at gmail dot com
2011-05-10 10:18 ` redi at gcc dot gnu.org [this message]
2011-05-10 10:38 ` jakub at gcc dot gnu.org
2011-05-10 11:03 ` vanceza at gmail dot com
2011-10-21 16:37 ` paolo.carlini at oracle dot com

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=bug-48940-4-OjnzfpGbuL@http.gcc.gnu.org/bugzilla/ \
    --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: 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).