Make the CCoInitializer constructor exception safe #2675
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The source code example is accompanied by the following comment:
, but the
CCoInitializer
constructor throws an exception when theCoInitializeEx
call completes with an error:I thought it may be a mistake in the comment, but the example below says otherwise:
There is no try/catch block that encloses the creation of the
CCoInitializer
class instance.The
CCoInitializer
implementation also indicates that the constructor shouldn't throw an exception:, otherwise, the usage of the
_coinitialized
flag is redundant - if an exception will be thrown at the constructor call, the destructor will never be called, so the_coinitialized
flag will never be used.