commit 983c592272eb59d39fd78c515e1f2701638879e0
author Chris Lattner <sabre@nondot.org> Sun Aug 23 21:53:47 2009 +0000
committer Chris Lattner <sabre@nondot.org> Sun Aug 23 21:53:47 2009 +0000
tree 1825e1faa278b8aee36b7c6191ee232165ced249
parent 28fb7c4a9a7ebabfd44d436028425862fbf01153

disuade people from using ostream.


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

docs/CodingStandards.html

diff --git a/docs/CodingStandards.html b/docs/CodingStandards.html
index ff707f3..8945216 100644
--- a/docs/CodingStandards.html
+++ b/docs/CodingStandards.html
@@ -990,12 +990,14 @@
 </ol>
 
 <p>Note that using the other stream headers (<tt>&lt;sstream&gt;</tt> for
-example) is allowed normally, it is just <tt>&lt;iostream&gt;</tt> that is
-causing problems.</p>
+example) is not problematic in this regard (just <tt>&lt;iostream&gt;</tt>).
+However, raw_ostream provides various APIs that are better performing for almost
+every use than std::ostream style APIs, so you should just use it for new
+code.</p>
 
-<p>In addition, new code should always
-use <a href="#ll_raw_ostream"><tt>raw_ostream</tt></a> or
-the <tt>llvm::MemoryBuffer</tt> API (for reading in files).</p>
+<p><b>New code should always
+use <a href="#ll_raw_ostream"><tt>raw_ostream</tt></a> for writing, or
+the <tt>llvm::MemoryBuffer</tt> API for reading files.</b></p>
 
 </div>