public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Joe Buck <jbuck@synopsys.com>
To: martin@mira.isdn.cs.tu-berlin.de (Martin von Loewis)
Cc: law@cygnus.com, rittle@comm.mot.com, egcs@cygnus.com
Subject: Re: Implications of tighter integration of libg++
Date: Mon, 09 Feb 1998 14:46:00 -0000	[thread overview]
Message-ID: <199802091952.LAA11877@atrus.synopsys.com> (raw)
In-Reply-To: <199802091507.QAA06511@mira.isdn.cs.tu-berlin.de>

> I'm not sure how the .h header files of libstdc++ should be handled;
> the standard allows to use them for backwards compatibility. Perhaps
> g++ will still need to special-case namespace std, and generate the
> appropriate aliases.

The goal of any such scheme is, as much as possible, to keep old programs
working.

One possibility is that iostream.h include <iostream>, followed by using
directives that import the names declared in <iostream>.  We should *not*
say "using namespace std;" as that imports all names.  Rather, just
things like

using std::istream;
using std::ostream;
using std::cin;
using std::cout;
using std::cerr;

etc.  I wouldn't advise 'using' for new facilities that didn't exist in
old libstdc++ versions (wide streams).

Then there's the problem that 'class ostream;' is now wrong.


  reply	other threads:[~1998-02-09 14:46 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1997-11-24 23:19 Loren J. Rittle
1997-11-25  6:52 ` Manfred.Hollstein
1998-02-09  2:22 ` Jeffrey A Law
1998-02-09  7:13   ` Martin von Loewis
1998-02-09 14:46     ` Joe Buck [this message]
1998-02-09 15:33       ` Martin von Loewis
1998-02-09 21:34         ` Joe Buck
1998-02-10  0:53           ` John A. Tamplin
1998-02-10 10:30             ` Joe Buck
1998-02-09 21:34         ` H.J. Lu
1998-02-09 11:54   ` Joe Buck
1998-02-09 14:46     ` H.J. Lu
     [not found] ` <5837.887019874.cygnus.egcs@hurl.cygnus.com>
1998-02-09 11:31   ` Jason Merrill
1998-02-09 11:54     ` Jeffrey A Law
1998-02-09 11:54       ` Jason Merrill
1998-02-09 15:33         ` Fred Fish

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=199802091952.LAA11877@atrus.synopsys.com \
    --to=jbuck@synopsys.com \
    --cc=egcs@cygnus.com \
    --cc=law@cygnus.com \
    --cc=martin@mira.isdn.cs.tu-berlin.de \
    --cc=rittle@comm.mot.com \
    /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).