From mboxrd@z Thu Jan  1 00:00:00 1970
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
Message-id: <199804101035.MAA03407@mira.isdn.cs.tu-berlin.de>
References: <199804091709.KAA24334@atrus.synopsys.com>
X-SW-Source: 1998-04/msg00428.html

> 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