Path: csiph.com!x330-a1.tempe.blueboxinc.net!usenet.pasdenom.info!gegeweb.org!de-l.enfer-du-nord.net!feeder2.enfer-du-nord.net!fu-berlin.de!uni-berlin.de!individual.net!not-for-mail
From: "Bo Persson" <bop@gmb.dk>
Newsgroups: comp.lang.c++
Subject: Re: Clarification on #include <ostream>
Date: Tue, 14 Jun 2011 18:00:52 +0200
Lines: 18
Message-ID: <95petfFu28U1@mid.individual.net>
References: <ostream-20110614175413@ram.dialup.fu-berlin.de>
X-Trace: individual.net Q91NYuay4m6ATyNmDl8Ngg0iKJmc8LKx0Uwhbv2S2CjyhzfniZ
Cancel-Lock: sha1:+Z0ILHphKQMKES4LEm3q4PijXBk=
X-Priority: 3
X-MSMail-Priority: Normal
X-Newsreader: Microsoft Outlook Express 6.00.2900.5931
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.6090
X-RFC2646: Format=Flowed; Original
X-Antivirus: avast! (VPS 110614-0, 2011-06-14), Outbound message
X-Antivirus-Status: Clean
Xref: x330-a1.tempe.blueboxinc.net comp.lang.c++:6745

Stefan Ram wrote:
>  The C++ standard from the 90s said that »#include <ostream>«
>  was required to use »<<« as in »::std::cout << 0«.
>
>  But since no implementation required this, it was often said
>  to be a defect in the standard.
>
>  Has this requirement been removed from the standard in the
>  meantime?

Yes, the new standard (C++11) requires <iostream> to include <istream> 
and <ostream>.



Bo Persson