From e0830c7c3be2ff075a3b2bdb5cb663465f88d342 Mon Sep 17 00:00:00 2001 From: Amir Livneh Date: Tue, 19 Feb 2019 14:32:19 -0500 Subject: [PATCH] Remove redundant word (#1334) --- CppCoreGuidelines.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/CppCoreGuidelines.md b/CppCoreGuidelines.md index ea2d1e3..4baef0b 100644 --- a/CppCoreGuidelines.md +++ b/CppCoreGuidelines.md @@ -21443,7 +21443,7 @@ In summary, no post-construction technique is perfect. The worst techniques dodg ### Discussion: Make base class destructors public and virtual, or protected and nonvirtual -Should destruction behave virtually? That is, should destruction through a pointer to a `base` class be allowed? If yes, then `base`'s destructor must be public in order to be callable, and virtual otherwise calling it results in undefined behavior. Otherwise, it should be protected so that only derived classes can invoke it in their own destructors, and nonvirtual since it doesn't need to behave virtually virtual. +Should destruction behave virtually? That is, should destruction through a pointer to a `base` class be allowed? If yes, then `base`'s destructor must be public in order to be callable, and virtual otherwise calling it results in undefined behavior. Otherwise, it should be protected so that only derived classes can invoke it in their own destructors, and nonvirtual since it doesn't need to behave virtually. ##### Example