From f211ce714c07d83444cbf5706651405c05ded223 Mon Sep 17 00:00:00 2001 From: Jordan Harris Date: Fri, 20 Nov 2015 14:00:57 -0500 Subject: [PATCH] Fix grammar in Appendix C... Discussion: Make base class destructors public and virtual, or protected and nonvirtual --- CppCoreGuidelines.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/CppCoreGuidelines.md b/CppCoreGuidelines.md index a7e8576..10afca8 100644 --- a/CppCoreGuidelines.md +++ b/CppCoreGuidelines.md @@ -13498,7 +13498,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 should 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 virtual. ##### Example