[llvm-commits] [llvm] r79866 - /llvm/trunk/docs/CodingStandards.html

Chris Lattner sabre at nondot.org
Sun Aug 23 14:53:47 PDT 2009


Author: lattner
Date: Sun Aug 23 16:53:47 2009
New Revision: 79866

URL: http://llvm.org/viewvc/llvm-project?rev=79866&view=rev
Log:
disuade people from using ostream.

Modified:
    llvm/trunk/docs/CodingStandards.html

Modified: llvm/trunk/docs/CodingStandards.html
URL: http://llvm.org/viewvc/llvm-project/llvm/trunk/docs/CodingStandards.html?rev=79866&r1=79865&r2=79866&view=diff

==============================================================================
--- llvm/trunk/docs/CodingStandards.html (original)
+++ llvm/trunk/docs/CodingStandards.html Sun Aug 23 16:53:47 2009
@@ -990,12 +990,14 @@
 </ol>
 
 <p>Note that using the other stream headers (<tt><sstream></tt> for
-example) is allowed normally, it is just <tt><iostream></tt> that is
-causing problems.</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>
+example) is not problematic in this regard (just <tt><iostream></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><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>
 





More information about the llvm-commits mailing list