@@ -180,6 +180,16 @@
             "redirect_url": "/cpp/cloud/cloud-and-web-programming-in-visual-cpp",
             "redirect_document_id": false
         },
+        {
+            "source_path": "docs/cpp/attributes2.md",
+            "redirect_url": "/cpp/cpp/attributes",
+            "redirect_document_id": false
+        },
+        {
+            "source_path": "docs/cpp/character-sets2.md",
+            "redirect_url": "/cpp/cpp/character-sets",
+            "redirect_document_id": false
+        },
         {
             "source_path": "docs/cpp/index.md",
             "redirect_url": "/cpp/cpp/cpp-language-reference",
 
@@ -36,7 +36,7 @@ Lets you specify the execution character set for your executable.
 ## Remarks  
  You can use the **/execution-charset** option to specify an execution character set. The execution character set is the encoding used for the text of your program that is input to the compilation phase after all preprocessing steps. This character set is used for the internal representation of any string or character literals in the compiled code. Set this option to specify the extended execution character set to use when your source files include characters that are not representable in the basic execution character set. You can use either the IANA or ISO character set name, or a dot (.) followed by a 3 to 5 digit decimal code page identifier to specify the character set to use. For a list of supported code page identifiers and character set names, see [Code Page Identifiers](http://msdn.microsoft.com/library/windows/desktop/dd317756).  
 
- By default, Visual Studio detects a byte-order mark to determine if the source file is in an encoded Unicode format, for example, UTF-16 or UTF-8. If no byte-order mark is found, it assumes the source file is encoded using the current user code page, unless you have specified a character set name or code page by using the **/source-charset** option or the **/utf-8** option. Visual Studio allows you to save your C++ source code by using any of several character encodings. For information about source and execution character sets, see [Character Sets](../../cpp/character-sets2.md) in the language documentation.  
+ By default, Visual Studio detects a byte-order mark to determine if the source file is in an encoded Unicode format, for example, UTF-16 or UTF-8. If no byte-order mark is found, it assumes the source file is encoded using the current user code page, unless you have specified a character set name or code page by using the **/source-charset** option or the **/utf-8** option. Visual Studio allows you to save your C++ source code by using any of several character encodings. For information about source and execution character sets, see [Character Sets](../../cpp/character-sets.md) in the language documentation.  
 
  If you want to set both the source character set and the execution character set to UTF-8, you can use the **/utf-8** compiler option as a shortcut. It is equivalent to specifying **/source-charset:utf-8 /execution-charset:utf-8** on the command line. Any of these options also enables the **/validate-charset** option by default.  
 
 
@@ -42,21 +42,19 @@ Without **/FC**, the diagnostic text would look similar to this diagnostic text:
 
 With **/FC**, the diagnostic text would look similar to this diagnostic text:
 
-- c:\test\compiler_option_FC.cpp(5) : error C2143: syntax error : missing ';' before '}'
+- c:\test\compiler_option_fc.cpp(5) : error C2143: syntax error : missing ';' before '}'
 
-**/FC** is also needed if you want to see the full path of a file name when using the &#95;&#95;FILE&#95;&#95; macro.  See [Predefined Macros](../../preprocessor/predefined-macros.md) for more information on &#95;&#95;FILE&#95;&#95;.
+ **/FC** is also needed if you want to see the full path of a file name when using the &#95;&#95;FILE&#95;&#95; macro. See [Predefined Macros](../../preprocessor/predefined-macros.md) for more information on &#95;&#95;FILE&#95;&#95;.
 
 The **/FC** option is implied by **/ZI**. For more information about **/ZI**, see [/Z7, /Zi, /ZI (Debug Information Format)](../../build/reference/z7-zi-zi-debug-information-format.md).
 
+**/FC** outputs full paths in lower case.
+
 ### To set this compiler option in the Visual Studio development environment
 
 1. Open the project's **Property Pages** dialog box. For details, see [Working with Project Properties](../../ide/working-with-project-properties.md).
 
-1. Expand the **Configuration Properties** node.
-
-1. Expand the **C/C++** node.
-
-1. Select the **Advanced** property page.
+1. Select the **Configuration Properties** > **C/C++** > **Advanced** property page.
 
 1. Modify the **Use Full Paths** property.
 
@@ -67,4 +65,4 @@ The **/FC** option is implied by **/ZI**. For more information about **/ZI**, se
 ## See Also
 
 [Compiler Options](../../build/reference/compiler-options.md)   
-[Setting Compiler Options](../../build/reference/setting-compiler-options.md)
+[Setting Compiler Options](../../build/reference/setting-compiler-options.md)
@@ -32,7 +32,7 @@ Controls the optimizations that LINK performs during a build.
  **REF** &#124; **NOREF**  
  **/OPT:REF** eliminates functions and data that are never referenced; **/OPT:NOREF** keeps functions and data that are never referenced.  
 
- When /OFT:REF is enabled, LINK removes unreferenced packaged functions and data. An object contains packaged functions and data (COMDATs) if it was compiled by using the [/Gy](../../build/reference/gy-enable-function-level-linking.md) option. This optimization is known as transitive COMDAT elimination. By default, **/OPT:REF** is enabled in non-debug builds. To override this default and keep unreferenced COMDATs in the program, specify **/OPT:NOREF**. You can use the [/INCLUDE](../../build/reference/include-force-symbol-references.md) option to override the removal of a specific symbol.  
+ When /OPT:REF is enabled, LINK removes unreferenced packaged functions and data. An object contains packaged functions and data (COMDATs) if it was compiled by using the [/Gy](../../build/reference/gy-enable-function-level-linking.md) option. This optimization is known as transitive COMDAT elimination. By default, **/OPT:REF** is enabled in non-debug builds. To override this default and keep unreferenced COMDATs in the program, specify **/OPT:NOREF**. You can use the [/INCLUDE](../../build/reference/include-force-symbol-references.md) option to override the removal of a specific symbol.  
 
  When **/OPT:REF** is enabled either explicitly or by default, a limited form of **/OPT:ICF** is enabled that only folds identical functions. If you want **/OPT:REF** but not **/OPT:ICF**, you must specify either **/OPT:REF,NOICF** or **/OPT:NOICF**.  
 
@@ -94,4 +94,4 @@ Controls the optimizations that LINK performs during a build.
 
 ## See Also  
  [Setting Linker Options](../../build/reference/setting-linker-options.md)   
- [Linker Options](../../build/reference/linker-options.md)
+ [Linker Options](../../build/reference/linker-options.md)
@@ -36,7 +36,7 @@ Lets you specify the source character set for your executable.
 ## Remarks  
  You can use the **/source-charset** option to specify an extended source character set to use when your source files include characters that are not represented in the basic source character set. The source character set is the encoding used to interpret the source text of your program into the internal representation used as input to the preprocessing phases before compilation. The internal representation is then converted to the execution character set to store string and character values in the executable. You can use either the IANA or ISO character set name, or a dot (.) followed by a 3 to 5 digit decimal code page identifier to specify the character set to use. For a list of supported code page identifiers and character set names, see [Code Page Identifiers](http://msdn.microsoft.com/library/windows/desktop/dd317756).  
 
- By default, Visual Studio detects a byte-order mark to determine if the source file is in an encoded Unicode format, for example, UTF-16 or UTF-8. If no byte-order mark is found, it assumes the source file is encoded using the current user code page, unless you specify a character set name or code page by using the **/source-charset** option. Visual Studio allows you to save your C++ source code by using any of several character encodings. For more information about source and execution character sets, see [Character Sets](../../cpp/character-sets2.md) in the language documentation.  
+ By default, Visual Studio detects a byte-order mark to determine if the source file is in an encoded Unicode format, for example, UTF-16 or UTF-8. If no byte-order mark is found, it assumes the source file is encoded using the current user code page, unless you specify a character set name or code page by using the **/source-charset** option. Visual Studio allows you to save your C++ source code by using any of several character encodings. For more information about source and execution character sets, see [Character Sets](../../cpp/character-sets.md) in the language documentation.  
 
  The source character set you supply must map the 7-bit ASCII characters to the same code points in your character set, or many compilation errors are likely to follow. Your source character set must also be mappable to the extended Unicode character set encodable by UTF-8. Characters that are not encodable in UTF-8 are represented by an implementation-specific substitute. The Microsoft compiler uses a question mark for these characters.  
 
 
@@ -29,7 +29,7 @@ Specifies both the source character set and the execution character set as UTF-8
 ## Remarks  
  You can use the **/utf-8** option to specify both the source and execution character sets as encoded by using UTF-8. It is equivalent to specifying **/source-charset:utf-8 /execution-charset:utf-8** on the command line. Any of these options also enables the **/validate-charset** option by default. For a list of supported code page identifiers and character set names, see [Code Page Identifiers](http://msdn.microsoft.com/library/windows/desktop/dd317756).  
 
- By default, Visual Studio detects a byte-order mark to determine if the source file is in an encoded Unicode format, for example, UTF-16 or UTF-8. If no byte-order mark is found, it assumes the source file is encoded using the current user code page, unless you have specified a code page by using **/utf-8** or the **/source-charset** option. Visual Studio allows you to save your C++ source code by using any of several character encodings. For information about source and execution character sets, see [Character Sets](../../cpp/character-sets2.md) in the language documentation.  
+ By default, Visual Studio detects a byte-order mark to determine if the source file is in an encoded Unicode format, for example, UTF-16 or UTF-8. If no byte-order mark is found, it assumes the source file is encoded using the current user code page, unless you have specified a code page by using **/utf-8** or the **/source-charset** option. Visual Studio allows you to save your C++ source code by using any of several character encodings. For information about source and execution character sets, see [Character Sets](../../cpp/character-sets.md) in the language documentation.  
 
 ### To set this compiler option in the Visual Studio development environment  
 
 
@@ -29,7 +29,7 @@ Validates that the source file text contains only characters representable as UT
 ## Remarks  
  You can use the **/validate-charset** option to validate that the source code contains only characters that can be represented in both the source character set and the execution character set. This check is enabled automatically when you specify **/source-charset**, **/execution-charset**, or **/utf-8** compiler options. You can explicitly disable this check by specifying the **/validate-charset-** option.  
 
- By default, Visual Studio detects a byte-order mark to determine if the source file is in an encoded Unicode format, for example, UTF-16 or UTF-8. If no byte-order mark is found, it assumes the source file is encoded using the current user code page, unless you have specified a code page by using **/utf-8** or the **/source-charset** option. Visual Studio allows you to save your C++ source code by using any of several character encodings. For information about source and execution character sets, see [Character Sets](../../cpp/character-sets2.md) in the language documentation. For a list of supported code page identifiers and character set names, see [Code Page Identifiers](http://msdn.microsoft.com/library/windows/desktop/dd317756).  
+ By default, Visual Studio detects a byte-order mark to determine if the source file is in an encoded Unicode format, for example, UTF-16 or UTF-8. If no byte-order mark is found, it assumes the source file is encoded using the current user code page, unless you have specified a code page by using **/utf-8** or the **/source-charset** option. Visual Studio allows you to save your C++ source code by using any of several character encodings. For information about source and execution character sets, see [Character Sets](../../cpp/character-sets.md) in the language documentation. For a list of supported code page identifiers and character set names, see [Code Page Identifiers](http://msdn.microsoft.com/library/windows/desktop/dd317756).  
 
  Visual Studio uses UTF-8 as the internal character encoding during conversion between the source character set and the execution character set. If a character in the source file cannot be represented in the execution character set, the UTF-8 conversion substitutes a question mark '?' character. The **/validate-charset** option causes the compilation to report a warning if this occurs.  
 
 
@@ -1,7 +1,7 @@
 ---
 title: "Math and floating-point support | Microsoft Docs"
 ms.custom: ""
-ms.date: "04/05/2018"
+ms.date: "04/06/2018"
 ms.technology: ["cpp-standard-libraries"]
 ms.tgt_pltfrm: ""
 ms.topic: "article"
@@ -24,8 +24,6 @@ Previous 16-bit versions of Microsoft C/C++ and Microsoft Visual C++ supported t
 
 ## Supported math and floating-point routines
 
-The CRT supports these floating point functions:
-
 |Routine|Use|
 |-|-|
 [abs, labs, llabs, _abs64](../c-runtime-library/reference/abs-labs-llabs-abs64.md)|Computes the absolute value of an integer type
 
@@ -1,7 +1,7 @@
 ---
 title: "Universal C runtime routines by category | Microsoft Docs"
 ms.custom: ""
-ms.date: "03/30/2018"
+ms.date: "04/06/2018"
 ms.technology: ["cpp-standard-libraries"]
 ms.topic: "article"
 f1_keywords: ["c.runtime"]
 
@@ -65,7 +65,7 @@ New attributes to silence warnings when an entity is not used, or to create a wa
 
 ### Using attribute namespaces without repetition
 
-New syntax to enable only a single namespace identifier in an attribute list. For more information, see [Attributes in C++](cpp/attributes2.md).
+New syntax to enable only a single namespace identifier in an attribute list. For more information, see [Attributes in C++](cpp/attributes.md).
 
 ### Structured bindings
 
@@ -1705,6 +1705,32 @@ int main() {
 
 ```
 
+### Variadic template constructor base class initialization list
+
+In previous editions of Visual Studio, a variadic template constructor base class initialization list that was missing template arguments was erroneously allowed without error. In Visual Studio 2017 version 15.7, a compiler error is raised.
+
+The following code example in Visual Studio 2017 version 15.7 raises *error C2614: D\<int>: illegal member initialization: 'B' is not a base or member*
+
+```cpp
+template<typename T>
+struct B {};
+
+template<typename T>
+struct D : B<T>
+{
+
+    template<typename ...C>
+    D() : B() {} // C2614. Missing template arguments to B.
+};
+
+D<int> d;
+
+```
+
+To fix the error, change the B() expression to B\<T>().
+
+
+
 ## See also
 
 [Visual C++ Language Conformance](visual-cpp-language-conformance.md)