From 031e7f5300fa420e335531bfdfcdcef7c1f4e42b Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Felix=20K=C3=A4lberer?= Date: Wed, 23 Sep 2015 19:39:24 +0200 Subject: [PATCH] Fix typos 1. thorough --> through 2. Add missing `)` 3. Fix "a a move assignment" (#90) --- CppCoreGuidelines.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/CppCoreGuidelines.md b/CppCoreGuidelines.md index f28366f..ec0544f 100644 --- a/CppCoreGuidelines.md +++ b/CppCoreGuidelines.md @@ -920,7 +920,7 @@ What if the connection goes down so than no logging output is produced? See Rule **Alternative**: Throw an exception. An exception cannot be ignored. **Alternative formulation**: Avoid passing information across an interface through non-local state. -Note that non-`const` member functions pass information to other member functions thorough their object's state. +Note that non-`const` member functions pass information to other member functions through their object's state. **Alternative formulation**: An interface should be a function or a set of functions. Functions can be template functions and sets of functions can be classes or class templates. @@ -2886,7 +2886,7 @@ These are *default operations*: * a copy constructor: `X(const X&)` * a copy assignment: `operator=(const X&)` * a move constructor: `X(X&&)` -* a a move assignment: `operator=(X&&)` +* a move assignment: `operator=(X&&)` * a destructor: `~X()` By default, the compiler defines each of these operations if it is used, but the default can be suppressed. @@ -8181,7 +8181,7 @@ Note that there is no return value that could contain an error code. The `File_handle` constructor might defined like this File_handle::File_handle(const string& name, const string& mode) - :f{fopen(name.c_str(),mode.c_str()} + :f{fopen(name.c_str(),mode.c_str())} { if (!f) throw runtime_error{"File_handle: could not open "S-+ name + " as " + mode"}