public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: "Joseph S. Myers" <jsm28@cam.ac.uk>
To: nobody@gcc.gnu.org
Cc: gcc-prs@gcc.gnu.org
Subject: Re: c++/3385: -std=foo doesn't work with C++
Date: Fri, 22 Jun 2001 17:46:00 -0000	[thread overview]
Message-ID: <20010623004601.3683.qmail@sourceware.cygnus.com> (raw)

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

From: "Joseph S. Myers" <jsm28@cam.ac.uk>
To: Daniel Elstner <daniel.elstner@gmx.net>
Cc: <gcc-gnats@gcc.gnu.org>,  <gcc-bugs@gcc.gnu.org>
Subject: Re: c++/3385: -std=foo doesn't work with C++
Date: Sat, 23 Jun 2001 01:42:21 +0100 (BST)

 On 23 Jun 2001, Daniel Elstner wrote:
 
 > When -std=foo is given g++ doesn't recognize most C++ constructs.
 > Includes of C++ specific headers do fail, too. For some odd reason
 > the new-style casts do still work.
 
 -std is not supported for C++.  Why did the documentation make you think 
 that is was?  Perhaps we can improve the documentation.
 
 It would make sense to support -std for C++, with possible values being 
 iso14882:1998 and g++98, but it's never going to make sense to specify a C 
 standard (ISO 9899) version when compiling C++, and there ought to be 
 appropriate errors given if you try to do so; the lack of error messages 
 is a bug.
 
 -- 
 Joseph S. Myers
 jsm28@cam.ac.uk
 


             reply	other threads:[~2001-06-22 17:46 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-06-22 17:46 Joseph S. Myers [this message]
  -- strict thread matches above, loose matches on Subject: below --
2002-04-26  4:04 nathan
2001-06-23  7:06 Gabriel Dos Reis
2001-06-23  2:16 Joseph S. Myers
2001-06-23  1:36 Neil Booth
2001-06-22 17:36 Daniel Elstner

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=20010623004601.3683.qmail@sourceware.cygnus.com \
    --to=jsm28@cam.ac.uk \
    --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).