From: Daniel Dunbar <daniel@zuster.org>
Date: Fri, 24 Jul 2009 23:54:34 +0000 (+0000)
Subject: Tweak, raw_ostream is a ostream, not iostream replacement
X-Git-Url: http://demsky.eecs.uci.edu/git/?a=commitdiff_plain;h=26fe866cec7e74a782700b7d03e378791b737908;p=oota-llvm.git

Tweak, raw_ostream is a ostream, not iostream replacement


git-svn-id: https://llvm.org/svn/llvm-project/llvm/trunk@77017 91177308-0d34-0410-b5e6-96231b3b80d8
---

diff --git a/docs/CodingStandards.html b/docs/CodingStandards.html
index 2d83f0bf62a..f66a7c2154e 100644
--- a/docs/CodingStandards.html
+++ b/docs/CodingStandards.html
@@ -948,10 +948,10 @@ it's better to use a literal <tt>'\n'</tt>.</p>
 
 <p>LLVM includes a lightweight, simple, and efficient stream implementation
 in <tt>llvm/Support/raw_ostream.h</tt> which provides all of the common features
-of <tt>std::iostream</tt>.  All new code should use <tt>raw_ostream</tt> instead
-of <tt>iostream</tt>.</p>
+of <tt>std::ostream</tt>.  All new code should use <tt>raw_ostream</tt> instead
+of <tt>ostream</tt>.</p>
 
-<p>Unlike <tt>std::iostream</tt>, <tt>raw_ostream</tt> is not a template and can
+<p>Unlike <tt>std::ostream</tt>, <tt>raw_ostream</tt> is not a template and can
 be forward declared as <tt>class raw_ostream</tt>.  Public headers should
 generally not include the <tt>raw_ostream</tt> header, but use forward
 declarations and constant references to <tt>raw_ostream</tt> instances.</p>