C++11: Compatibility with (C++03 => MSVC)
authorDuncan P. N. Exon Smith <dexonsmith@apple.com>
Thu, 17 Apr 2014 18:02:36 +0000 (18:02 +0000)
committerDuncan P. N. Exon Smith <dexonsmith@apple.com>
Thu, 17 Apr 2014 18:02:36 +0000 (18:02 +0000)
git-svn-id: https://llvm.org/svn/llvm-project/llvm/trunk@206481 91177308-0d34-0410-b5e6-96231b3b80d8

docs/CodingStandards.rst

index a90e94b450ceaee697c012acbf84bb20d7bc4696..0fcca0330f4bc83370ce1e623abc92f61fff9859 100644 (file)
@@ -1284,9 +1284,9 @@ method will never be implemented. This enables other checks like
 ``-Wunused-private-field`` to run correctly on classes that contain these
 methods.
 
-To maintain compatibility with C++03, ``LLVM_DELETED_FUNCTION`` should be used
-which will expand to ``= delete`` if the compiler supports it. These methods
-should still be declared private. Example of the uncopyable pattern:
+For compatibility with MSVC, ``LLVM_DELETED_FUNCTION`` should be used which
+will expand to ``= delete`` on compilers that support it. These methods should
+still be declared private. Example of the uncopyable pattern:
 
 .. code-block:: c++