maxjhandsome
/
llvm-project
forked from OSchip/llvm-project
1
0
Fork 0
Code Issues Pull Requests Packages Releases Wiki Activity

disuade people from using ostream. 

llvm-svn: 79866
This commit is contained in:
Chris Lattner 2009-08-23 21:53:47 +00:00
parent 1518c64a23
commit 5db2ff5037
1 changed files with 7 additions and 5 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

12
llvm/docs/CodingStandards.html
View File

@ -990,12 +990,14 @@ library. There are two problems with this:</p>
</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>