public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: Martin Sebor <sebor@roguewave.com>
To: nobody@gcc.gnu.org
Cc: gcc-prs@gcc.gnu.org,
Subject: Re: libstdc++/9975: time defined in :: namespace
Date: Fri, 07 Mar 2003 17:46:00 -0000	[thread overview]
Message-ID: <20030307174601.6676.qmail@sources.redhat.com> (raw)

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

From: Martin Sebor <sebor@roguewave.com>
To: bangerth@dealii.org,  gcc-gnats@gcc.gnu.org
Cc:  
Subject: Re: libstdc++/9975: time defined in :: namespace
Date: Fri, 07 Mar 2003 10:36:59 -0700

 FWIW, the problem is that according to 17.4.1.2 and 17.4.2.1,
 Footnote 160, the <cxxx> headers must declare symbols only
 namespace std, while the <xxx.h> headers must declare the
 same symbols in both the global namespace and namespace std.
 AFAIK, this can only be done correctly (as if) by inclusion
 followed by using declarations, i.e.,
 
     // <cxxx>
     namespace std {
     extern "C" void foo ();
     // ...
     }
 
     // <xxx.h>
     #include <cxxx>
     using std::foo;
     // ...
 
 Regards
 Martin
 
 PS A better test case might be
 
 $ cat t.cpp; g++ -c t.cpp
 #include <ctime>
 enum { time };
 
 t.cpp:2: `time' redeclared as different kind of symbol
 /usr/include/time.h:81: previous declaration of `time_t time(time_t*)'
 
 > http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc&pr=9975
 


             reply	other threads:[~2003-03-07 17:46 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-03-07 17:46 Martin Sebor [this message]
  -- strict thread matches above, loose matches on Subject: below --
2003-03-10 20:46 bangerth
2003-03-06 14:16 bangerth

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=20030307174601.6676.qmail@sources.redhat.com \
    --to=sebor@roguewave.com \
    --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).