From 098dd3ee900bc13ae190f68712408e332b6cb5cd Mon Sep 17 00:00:00 2001
From: Bjarne Stroustrup <bjarne@stroustrup.com>
Date: Sun, 16 Apr 2017 21:50:52 -0400
Subject: [PATCH] add example to NR.1

---
 CppCoreGuidelines.md | 20 +++++++++++++++++++-
 1 file changed, 19 insertions(+), 1 deletion(-)

diff --git a/CppCoreGuidelines.md b/CppCoreGuidelines.md
index 03040e4..95f9da3 100644
--- a/CppCoreGuidelines.md
+++ b/CppCoreGuidelines.md
@@ -17518,10 +17518,28 @@ This leads to longer programs and more errors caused by uninitialized and wrongl
 
 ##### Example, bad
 
-    ???
+   int use(int x)
+   {
+       int i;
+       char c;
+       double d;
+
+       // ... some stuff ...
+
+       if (x<i) {
+           // ...
+           i=  f(x,d);
+       }
+       if (i<x) {
+           // ...
+           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.
+Unfortunately, compilers cannot catch all such errors and unfortunately, the bugs aren't always as simple to spot as in this small example.
 
 
 ##### Alternative