public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
* [Bug c++/52166] New: c++0x required to import standard c++ headers?
@ 2012-02-08  1:19 scovich at gmail dot com
  2012-02-08  9:01 ` [Bug c++/52166] " redi at gcc dot gnu.org
                   ` (2 more replies)
  0 siblings, 3 replies; 4+ messages in thread
From: scovich at gmail dot com @ 2012-02-08  1:19 UTC (permalink / raw)
  To: gcc-bugs

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

             Bug #: 52166
           Summary: c++0x required to import standard c++ headers?
    Classification: Unclassified
           Product: gcc
           Version: 4.6.2
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: c++
        AssignedTo: unassigned@gcc.gnu.org
        ReportedBy: scovich@gmail.com


Several of the standard C++ wrapper versions of C headers can only be imported
with c++0x support enabled (tested on both cygwin and x86_64-linux):

#error This file requires compiler and library support for the upcoming ISO C++
standard, C++0x. This support is currently experimental, and must be enabled
with the -std=c++0x or -std=gnu++0x compiler options.

Workaround is to #include <foo.h> instead of <cfoo>, but it's annoying given
that the former is supposedly The Right Way for C++ programs to bring in the
header.

Affected files:

ccomplex
cfenv
cinttypes
cstdint


^ permalink raw reply	[flat|nested] 4+ messages in thread

* [Bug c++/52166] c++0x required to import standard c++ headers?
  2012-02-08  1:19 [Bug c++/52166] New: c++0x required to import standard c++ headers? scovich at gmail dot com
@ 2012-02-08  9:01 ` redi at gcc dot gnu.org
  2012-02-08 10:22 ` rguenth at gcc dot gnu.org
  2012-02-08 10:58 ` redi at gcc dot gnu.org
  2 siblings, 0 replies; 4+ messages in thread
From: redi at gcc dot gnu.org @ 2012-02-08  9:01 UTC (permalink / raw)
  To: gcc-bugs

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

--- Comment #1 from Jonathan Wakely <redi at gcc dot gnu.org> 2012-02-08 09:01:39 UTC ---
(In reply to comment #0)
> Workaround is to #include <foo.h> instead of <cfoo>, but it's annoying given
> that the former is supposedly The Right Way for C++ programs to bring in the
> header.

It's the right way for C++11 programs to bring in the headers - the headers
don't exist in C++03


^ permalink raw reply	[flat|nested] 4+ messages in thread

* [Bug c++/52166] c++0x required to import standard c++ headers?
  2012-02-08  1:19 [Bug c++/52166] New: c++0x required to import standard c++ headers? scovich at gmail dot com
  2012-02-08  9:01 ` [Bug c++/52166] " redi at gcc dot gnu.org
@ 2012-02-08 10:22 ` rguenth at gcc dot gnu.org
  2012-02-08 10:58 ` redi at gcc dot gnu.org
  2 siblings, 0 replies; 4+ messages in thread
From: rguenth at gcc dot gnu.org @ 2012-02-08 10:22 UTC (permalink / raw)
  To: gcc-bugs

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

Richard Guenther <rguenth at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|UNCONFIRMED                 |RESOLVED
         Resolution|                            |INVALID

--- Comment #2 from Richard Guenther <rguenth at gcc dot gnu.org> 2012-02-08 10:22:28 UTC ---
Correct.


^ permalink raw reply	[flat|nested] 4+ messages in thread

* [Bug c++/52166] c++0x required to import standard c++ headers?
  2012-02-08  1:19 [Bug c++/52166] New: c++0x required to import standard c++ headers? scovich at gmail dot com
  2012-02-08  9:01 ` [Bug c++/52166] " redi at gcc dot gnu.org
  2012-02-08 10:22 ` rguenth at gcc dot gnu.org
@ 2012-02-08 10:58 ` redi at gcc dot gnu.org
  2 siblings, 0 replies; 4+ messages in thread
From: redi at gcc dot gnu.org @ 2012-02-08 10:58 UTC (permalink / raw)
  To: gcc-bugs

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

--- Comment #3 from Jonathan Wakely <redi at gcc dot gnu.org> 2012-02-08 10:58:16 UTC ---
N.B. if we enabled <cstdint> in C++03 mode users would (rightly) complain that
it makes it harder to write portable programs, and it would be a problem for
autoconf-style tests which check for the existence of <cstdint> to determine
whether a C++11 compiler is being used.


^ permalink raw reply	[flat|nested] 4+ messages in thread

end of thread, other threads:[~2012-02-08 10:58 UTC | newest]

Thread overview: 4+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2012-02-08  1:19 [Bug c++/52166] New: c++0x required to import standard c++ headers? scovich at gmail dot com
2012-02-08  9:01 ` [Bug c++/52166] " redi at gcc dot gnu.org
2012-02-08 10:22 ` rguenth at gcc dot gnu.org
2012-02-08 10:58 ` redi at gcc dot gnu.org

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).