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

use markdown link instead of html link

Browse Source
This commit is contained in:
Thibault Kruse
2015-09-27 20:05:11 +02:00
parent 7c0d7830e2
commit a68ace40df
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

@@ -3374,7 +3374,7 @@ The standard library requires that all classes it deals with have destructors th
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 be a real practical problem: For example, what about a sockets 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 <a =href="#Sd-dtor">discussion</a>. 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.
If at all possible, consider failure to close/cleanup a fundamental design error and terminate. If at all possible, consider failure to close/cleanup a fundamental design error and terminate.