public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: pme@gcc.gnu.org To: pme@gcc.gnu.org Cc: gcc-prs@gcc.gnu.org Subject: Re: libstdc++/3026 Date: Tue, 05 Jun 2001 09:36:00 -0000 [thread overview] Message-ID: <20010605163600.25061.qmail@sourceware.cygnus.com> (raw) The following reply was made to PR libstdc++/3026; it has been noted by GNATS. From: pme@gcc.gnu.org To: bkoz@gcc.gnu.org, cate@debian.org, gcc-gnats@gcc.gnu.org, pme@gcc.gnu.org Cc: Subject: Re: libstdc++/3026 Date: 5 Jun 2001 16:35:36 -0000 Synopsis: namespace errors in <complext.h> and other .h State-Changed-From-To: open->analyzed State-Changed-By: pme State-Changed-When: Tue Jun 5 09:35:36 2001 State-Changed-Why: Egads. A bunch of problems conspiring together. On one hand, the c_std headers are being used, which are known to be nonconforming in this respect. Replacing the installed std_cstddef.h with the one from c_shadow solves the initial 'size_t/ptrdiff_t not declared' problem. On the other hand, /usr/include/stdlib.h starts giving parse errors due to its lack of knowledge about namespace std and namespaces in general; unqualified use of 'size_t' breaks in this case. Gripping hand, I'm not entirely certain that namespace foo { #include <something_standard.h> } is permitted in userland by [17.4.1.1]/2, "All library entities ... are defined within the namespace std or namespaces nested within namespace std." Here we're nesting namespace std inside another namespace. If this code is valid, then I think this becomes another "funky C wrapping header problem" PR. http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view&pr=3026&database=gcc
next reply other threads:[~2001-06-05 9:36 UTC|newest] Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top 2001-06-05 9:36 pme [this message] -- strict thread matches above, loose matches on Subject: below -- 2001-06-07 9:26 libstdc++/3026 Gabriel Dos Reis 2001-06-07 8:06 libstdc++/3026 Catenazzi, Giacomo Amabile 2001-06-07 5:46 libstdc++/3026 Gabriel Dos Reis 2001-06-07 0:56 libstdc++/3026 Giacomo Catenazzi 2001-06-06 11:16 libstdc++/3026 Gabriel Dos Reis 2001-06-06 8:36 libstdc++/3026 Giacomo Catenazzi 2001-06-05 13:16 libstdc++/3026 Gabriel Dos Reis 2001-06-05 10:06 libstdc++/3026 Benjamin Kosnik 2001-06-04 11:06 libstdc++/3026 bkoz
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=20010605163600.25061.qmail@sourceware.cygnus.com \ --to=pme@gcc.gnu.org \ --cc=gcc-prs@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).