public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: "Catenazzi, Giacomo Amabile" <giacomoamabile.catenazzi@cepe.mavt.ethz.ch>
To: pme@gcc.gnu.org
Cc: gcc-prs@gcc.gnu.org
Subject: Re: libstdc++/3026
Date: Thu, 07 Jun 2001 08:06:00 -0000	[thread overview]
Message-ID: <20010607150604.1202.qmail@sourceware.cygnus.com> (raw)

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

From: "Catenazzi, Giacomo Amabile"
	 <giacomoamabile.catenazzi@cepe.mavt.ethz.ch>
To: Gabriel Dos Reis <Gabriel.Dos-Reis@cmla.ens-cachan.fr>
Cc: cate@dplanet.ch, gcc-gnats@gcc.gnu.org
Subject: Re: libstdc++/3026
Date: Thu, 07 Jun 2001 17:17:08 +0200

 Gabriel Dos Reis wrote:
 > 
 > Giacomo Catenazzi <cate@math.ethz.ch> writes:
 > 
 > | Gabriel Dos Reis wrote:
 > |
 > | An other problem: Should '#include <complex>' define functions/classes
 > | in std namespace, without exporting it in global namespace?
 > | Now <complex> and <complex.h> are the same, and both use global
 > | namespace.
 > 
 > There is nothing named <complex.h> specified by C++.  The standard
 > header <complex> defines its entities only in namespace std.  I
 > strongly suggest you stick to those standard interfaces.
 > 
 
 Ok. Sorry. Confused about different version of library.
 BTW
 .  #include <complex>
 .  int foo(std::complex<double> z) {
 .    return int(real(z));
 .  }
 This code will compile on http://www.codesourcery.com/gcc-compile.shtml
 thus 'real' is in also on global namespace.
 [But I'm not sure about the standard: the functions/classes should be in
 std namespace, but they can be exported implicitly in the global
 namespace?]
 
 	giacomo


             reply	other threads:[~2001-06-07  8:06 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-06-07  8:06 Catenazzi, Giacomo Amabile [this message]
  -- strict thread matches above, loose matches on Subject: below --
2001-06-07  9:26 libstdc++/3026 Gabriel Dos Reis
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-05  9:36 libstdc++/3026 pme
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=20010607150604.1202.qmail@sourceware.cygnus.com \
    --to=giacomoamabile.catenazzi@cepe.mavt.ethz.ch \
    --cc=gcc-prs@gcc.gnu.org \
    --cc=pme@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).