This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: C++ library for egcs
- To: martin at mira dot isdn dot cs dot tu-berlin dot de (Martin von Loewis)
- Subject: Re: C++ library for egcs
- From: Joe Buck <jbuck at synopsys dot com>
- Date: Fri, 10 Apr 98 9:46:36 PDT
- Cc: jbuck at synopsys dot com, egcs at cygnus dot 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.
No, in compliant C++ code, is is *not* correct. ostream is now a typedef!
ostream is really basic_ostream<char>. This breaks the world.
> The problem comes when they include <iostream.h>, as it will have a
> using declaration for std::iostream.
No, you are missing the point. That is not the major problem.