[Bug libstdc++/52195] New: <cstdio> doesn't put stdio, stderr and stdin in the std namespace

[Bug libstdc++/52195] New: <cstdio> doesn't put stdio, stderr and stdin in the std namespace

[nospam.kotarou.dono at gmail dot com]

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

             Bug #: 52195
           Summary: <cstdio> doesn't put stdio, stderr and stdin in the
                    std namespace
    Classification: Unclassified
           Product: gcc
           Version: 4.7.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: libstdc++
        AssignedTo: unassigned@gcc.gnu.org
        ReportedBy: nospam.kotarou.dono@gmail.com


<cstdio> doesn't seem to put stdio, stderr and stdin in the std namespace.

Example:
$ printf '
#include <cstdio>
int main()
{
    std::fputs("Hi there.", std::stdout);
    return 0;
}
' | g++ -xc++ - -o - > /dev/null
<stdin>: In function ‘int main()’:
<stdin>:5:16: error: ‘stdout’ is not a member of ‘std’
<stdin>:5:16: note: suggested alternative:
In file included from /usr/include/c++/4.7/cstdio:44:0,
                 from <stdin>:2:
/usr/include/stdio.h:166:25: note:   ‘stdout’

$ g++ -v
Using built-in specs.
COLLECT_GCC=g++
COLLECT_LTO_WRAPPER=/usr/lib/gcc/x86_64-linux-gnu/4.7/lto-wrapper
Target: x86_64-linux-gnu
Configured with: ../src/configure -v --with-pkgversion='Ubuntu/Linaro
4.7-20120205-1' --with-bugurl=file:///usr/share/doc/gcc-4.7/README.Bugs
--enable-languages=c,c++,fortran,objc,obj-c++,go --prefix=/usr
--program-suffix=-4.7 --enable-shared --enable-linker-build-id
--with-system-zlib --libexecdir=/usr/lib --without-included-gettext
--enable-threads=posix --with-gxx-include-dir=/usr/include/c++/4.7
--libdir=/usr/lib --enable-nls --with-sysroot=/ --enable-clocale=gnu
--enable-libstdcxx-debug --enable-libstdcxx-time=yes --enable-plugin
--enable-objc-gc --disable-werror --with-arch-32=i686 --with-tune=generic
--enable-checking=release --build=x86_64-linux-gnu --host=x86_64-linux-gnu
--target=x86_64-linux-gnu
Thread model: posix
gcc version 4.7.0 20120205 (experimental) [trunk revision 183903]
(Ubuntu/Linaro 4.7-20120205-1)

[Bug libstdc++/52195] <cstdio> doesn't put stdio, stderr and stdin in the std namespace

[jakub at gcc dot gnu.org]

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

Jakub Jelinek <jakub at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |jakub at gcc dot gnu.org

--- Comment #1 from Jakub Jelinek <jakub at gcc dot gnu.org> 2012-02-10 07:50:09 UTC ---
Why do you think that is a bug?  The C++98 standard, in [lib.c.files] says that
stderr, stdin and stdout are macros and obviously macros can't be in any
namespace.

[Bug libstdc++/52195] <cstdio> doesn't put stdio, stderr and stdin in the std namespace

[jakub at gcc dot gnu.org]

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

Jakub Jelinek <jakub at gcc dot gnu.org> changed:

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

--- Comment #2 from Jakub Jelinek <jakub at gcc dot gnu.org> 2012-02-10 07:52:10 UTC ---
See also [lib.contents]:
"The C++ Standard Library provides definitions for the following types of
entities: Macros, Values, Types, Templates, Classes, Functions, Objects.
All library entities except macros, operator new and operator delete are
defined within the namespace std or namespaces nested within namespace std."

[Bug libstdc++/52195] <cstdio> doesn't put stdio, stderr and stdin in the std namespace

[nospam.kotarou.dono at gmail dot com]

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

--- Comment #3 from nospam.kotarou.dono at gmail dot com 2012-02-10 08:21:40 UTC ---
Oh, because simply doing:
namespace std
{
    using ::stdout;
    using ::stderr;
    using ::stdin;
}
seemed to work fine for me on both linux and windows so I thought they wouldn't
be macros. I'm not too good at checking standards though :p