Mirrors/CppCoreGuidelines
1
0
Fork 0
mirror of https://github.com/isocpp/CppCoreGuidelines.git synced 2025-12-17 12:44:42 +03:00
Code Issues Actions Packages Projects Releases Wiki Activity

Merge pull request #468 from mpark/C.36

Browse Source 
C.36: Fixed a couple of typos.
This commit is contained in:
Gabriel Dos Reis
2015-12-18 07:48:18 -08:00
parent 5b4e9ae9bd 5f7432b131
commit f37d053c86
1 changed files with 1 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files

2
CppCoreGuidelines.md
View File

@@ -3839,7 +3839,7 @@ The standard library requires that all classes it deals with have destructors th
Many have tried to devise a fool-proof scheme for dealing with failure in destructors. Many have tried to devise a fool-proof scheme for dealing with failure in destructors.
None have succeeded to come up with a general scheme. None have succeeded to come up with a general scheme.
This can be be a real practical problem: For example, what about a sockets that won't close? This can be a real practical problem: For example, what about a socket that won't close?
The writer of a destructor does not know why the destructor is called and cannot "refuse to act" by throwing an exception. The writer of a destructor does not know why the destructor is called and cannot "refuse to act" by throwing an exception.
See [discussion](#Sd-dtor). See [discussion](#Sd-dtor).
To make the problem worse, many "close/release" operations are not retryable. To make the problem worse, many "close/release" operations are not retryable.