From 04537cdb111458254f321c7e7f4fcbea3736a5a2 Mon Sep 17 00:00:00 2001 From: Sergey Zubkov Date: Mon, 17 Apr 2017 23:37:17 -0400 Subject: [PATCH] travis CI fixes --- CppCoreGuidelines.md | 11 ++++++----- 1 file changed, 6 insertions(+), 5 deletions(-) diff --git a/CppCoreGuidelines.md b/CppCoreGuidelines.md index 143673d..dd8ae36 100644 --- a/CppCoreGuidelines.md +++ b/CppCoreGuidelines.md @@ -158,7 +158,7 @@ You can look at design concepts used to express the rules: * assertion: ??? * error: ??? -* exception: [exception guarantee[(???)] +* exception: exception guarantee (???) * failure: ??? * invariant: ??? * leak: ??? @@ -17320,7 +17320,7 @@ those sequences are allocated and stored. ##### Enforcement ??? - + ### SL.str.3: Use `zstring` or `czstring` to refer to a C-style, zero-terminated, sequence of characters ##### Reason @@ -17360,7 +17360,7 @@ This is one of the major sources of bugs in C and C++ programs, so it is worthwh * Flag uses of `[]` on a `char*` * Flag uses of `delete` on a `char*` * Flag uses of `free()` on a `char*` - + ### SL.str.4: Use `char*` to refer to a single character ##### Reason @@ -17390,7 +17390,7 @@ See [`zstring`](#Rstr-zstring), [`string`](#Rstr-string), and [`string_span`](#R ##### Enforcement * Flag uses of `[]` on a `char*` - + ### Sl.str.5: Use `std::byte` to refer to byte values that do not necessarily represent characters ##### Reason @@ -17428,6 +17428,7 @@ C++17 ##### Enforcement ??? + ### Sl.str.11: Use `gsl::string_span` rather than `std::string_view` when you need to mutate a string ##### Reason @@ -17630,7 +17631,7 @@ This leads to longer programs and more errors caused by uninitialized and wrongl i = g(x, c); } return i; - } + } The larger the distance between the uninitialized variable and its use, the larger the chance of a bug. Fortunately, compilers catch many "used before set" errors.