6502/llvm-6502
1
0
Fork 0
mirror of https://github.com/c64scene-ar/llvm-6502.git synced 2025-08-09 11:25:55 +00:00
Code Issues Projects Releases Wiki Activity

disuade people from using ostream.

Browse Source 
git-svn-id: https://llvm.org/svn/llvm-project/llvm/trunk@79866 91177308-0d34-0410-b5e6-96231b3b80d8
This commit is contained in:
Chris Lattner
2009-08-23 21:53:47 +00:00
parent 28fb7c4a9a
commit 983c592272
1 changed files with 7 additions and 5 deletions
Download Patch File Download Diff File Expand all files Collapse all files

12
docs/CodingStandards.html
View File

@@ -990,12 +990,14 @@ library. There are two problems with this:</p>
</ol> </ol>
<p>Note that using the other stream headers (<tt>&lt;sstream&gt;</tt> for <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 example) is not problematic in this regard (just <tt>&lt;iostream&gt;</tt>).
causing problems.</p> 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 <p><b>New code should always
use <a href="#ll_raw_ostream"><tt>raw_ostream</tt></a> or use <a href="#ll_raw_ostream"><tt>raw_ostream</tt></a> for writing, or
the <tt>llvm::MemoryBuffer</tt> API (for reading in files).</p> the <tt>llvm::MemoryBuffer</tt> API for reading files.</b></p>
</div> </div>