From 221b239342d6089550ad7f49cbf49509111d3f7e Mon Sep 17 00:00:00 2001 From: Chris Lattner Date: Tue, 16 Nov 2010 22:19:06 +0000 Subject: [PATCH] update coding standards. Partial specialization is now ok, though possibly not a good idea. git-svn-id: https://llvm.org/svn/llvm-project/llvm/trunk@119398 91177308-0d34-0410-b5e6-96231b3b80d8 --- docs/CodingStandards.html | 7 ++++--- 1 file changed, 4 insertions(+), 3 deletions(-) diff --git a/docs/CodingStandards.html b/docs/CodingStandards.html index 416c29b7bed..44a55a55857 100644 --- a/docs/CodingStandards.html +++ b/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.

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.

+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.