diff options
| author | Chris Lattner <sabre@nondot.org> | 2009-08-23 21:53:47 +0000 |
|---|---|---|
| committer | Chris Lattner <sabre@nondot.org> | 2009-08-23 21:53:47 +0000 |
| commit | 5db2ff50372c14b47be88974ca0e2c2178e65628 (patch) | |
| tree | e059125110e9178191c25fb722c473d8abc7bd04 /llvm/docs | |
| parent | 1518c64a23f9899cb79069d364377e02bb578c3d (diff) | |
| download | bcm5719-llvm-5db2ff50372c14b47be88974ca0e2c2178e65628.tar.gz bcm5719-llvm-5db2ff50372c14b47be88974ca0e2c2178e65628.zip | |
disuade people from using ostream.
llvm-svn: 79866
Diffstat (limited to 'llvm/docs')
| -rw-r--r-- | llvm/docs/CodingStandards.html | 14 |
1 files changed, 8 insertions, 6 deletions
diff --git a/llvm/docs/CodingStandards.html b/llvm/docs/CodingStandards.html index ff707f3a84f..894521650a6 100644 --- a/llvm/docs/CodingStandards.html +++ b/llvm/docs/CodingStandards.html @@ -990,12 +990,14 @@ library. There are two problems with this:</p> </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> |
