From: Martin von Loewis <martin@mira.isdn.cs.tu-berlin.de>
To: jbuck@synopsys.com
Cc: egcs@cygnus.com
Subject: Re: C++ library for egcs
Date: Fri, 10 Apr 1998 07:27:00 -0000 [thread overview]
Message-ID: <199804101035.MAA03407@mira.isdn.cs.tu-berlin.de> (raw)
In-Reply-To: <199804091709.KAA24334@atrus.synopsys.com>
> The practice I'm most concerned about is that users tend to write
>
> class ostream;
>
> Historically this has been a wise thing to do -- compilation time on
> big projects is improved greatly if you do this, and the committee
> broke it.
How much of a real problem is this? In a compliant C++ library, this
declaration in itself is correct, even if you include <iostream>
later.
The problem comes when they include <iostream.h>, as it will have a
using declaration for std::iostream. With a using directive, it would
be still correct. Of course, the problem comes later when you actually
use ostream, and it isn't defined.
I think there is no better way than telling users to include iosfwd.
If you use more than one compiler, you'd have to feature-test presence
of iosfwd in your code, anyway.
Martin
next prev parent reply other threads:[~1998-04-10 7:27 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
1998-04-08 23:35 Ulrich Drepper
1998-04-09 19:56 ` Joe Buck
1998-04-10 7:27 ` Martin von Loewis [this message]
1998-04-10 12:35 ` Joe Buck
1998-04-10 12:35 ` Martin von Loewis
1998-04-10 12:35 ` Joe Buck
1998-04-13 12:28 ` Martin von Loewis
1998-04-09 9:03 Daniel Egger
1998-04-09 14:17 Benjamin Redelings I
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=199804101035.MAA03407@mira.isdn.cs.tu-berlin.de \
--to=martin@mira.isdn.cs.tu-berlin.de \
--cc=egcs@cygnus.com \
--cc=jbuck@synopsys.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).