From 66ca2b5f6a4d73028392457035fb3c46f0c34f24 Mon Sep 17 00:00:00 2001 From: Matthias Kluwe Date: Tue, 24 Nov 2015 18:34:56 +0100 Subject: [PATCH] Fix grammar in I.22 --- CppCoreGuidelines.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/CppCoreGuidelines.md b/CppCoreGuidelines.md index db3b362..f7437e0 100644 --- a/CppCoreGuidelines.md +++ b/CppCoreGuidelines.md @@ -1596,8 +1596,8 @@ Complex initialization can lead to undefined order of execution. const X x = g(y); // read y; write x -Since `x` and `y` are in different translation units the order of calls to `f()` and `g()` are undefined; -once will access and uninitialized `const`. +Since `x` and `y` are in different translation units the order of calls to `f()` and `g()` is undefined; +one will access an uninitialized `const`. This particular example shows that the order-of-initialization problem for global (namespace scope) objects is not limited to global *variables*. ##### Note