summaryrefslogtreecommitdiffstats
path: root/llvm/docs/CodingStandards.html
diff options
context:
space:
mode:
authorChris Lattner <sabre@nondot.org>2010-11-16 22:19:06 +0000
committerChris Lattner <sabre@nondot.org>2010-11-16 22:19:06 +0000
commit44c2241cd44e11b3529b6ad86a7b92a9d2c99d5c (patch)
treefadcdd79571f0e852bd4c7551e6823a6e47e7c0e /llvm/docs/CodingStandards.html
parent5b791f6e64ac251d87843e001d4e031ae9974bf1 (diff)
downloadbcm5719-llvm-44c2241cd44e11b3529b6ad86a7b92a9d2c99d5c.tar.gz
bcm5719-llvm-44c2241cd44e11b3529b6ad86a7b92a9d2c99d5c.zip
update coding standards. Partial specialization is now ok,
though possibly not a good idea. llvm-svn: 119398
Diffstat (limited to 'llvm/docs/CodingStandards.html')
-rw-r--r--llvm/docs/CodingStandards.html7
1 files changed, 4 insertions, 3 deletions
diff --git a/llvm/docs/CodingStandards.html b/llvm/docs/CodingStandards.html
index 416c29b7bed..44a55a55857 100644
--- a/llvm/docs/CodingStandards.html
+++ b/llvm/docs/CodingStandards.html
@@ -397,9 +397,10 @@ portable code. If there are cases where it isn't possible to write portable
code, isolate it behind a well defined (and well documented) interface.</p>
<p>In practice, this means that you shouldn't assume much about the host
-compiler, including its support for "high tech" features like partial
-specialization of templates. If these features are used, they should only be
-an implementation detail of a library which has a simple exposed API.</p>
+compiler, and Visual Studio tends to be the lowest common denominator.
+If advanced features are used, they should only be an implementation detail of
+a library which has a simple exposed API, and preferably be buried in
+libSystem.</p>
</div>
OpenPOWER on IntegriCloud