Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

GCC 6.3 warning - throwing an exception from noexcept method #45

Merged
merged 3 commits into from
Dec 13, 2017

Conversation

smradCZ
Copy link
Contributor

@smradCZ smradCZ commented Nov 27, 2017

Error will be logged instead of throwing an exception from noexcept
method Statement::close() and program will be terminated by
calling std::terminate directly.
It's fixed because is not intended to throw messages directly from
methods with noexcept specifier and this is also checked by compilers
with -Wall option by default.

It fixes #41 also.

This is one step from many in process of porting package to debian-stretch.

Error will be logged instead of throwing an exception from noexcept
method Statement::close() and program will be terminated by
calling std::terminate directly.
It's fixed because is not intended to throw messages directly from
methods with noexcept specifier and this is also checked by compilers
with -Wall option by default.
@@ -703,7 +711,7 @@ namespace SuperiorMySqlpp {
}

public:
static bool isDestoyed()
static bool isDestroyed()
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This is kind of unrelated change. Please put it into another pull request.
Also, this is unfortunately interface change and thus this should implicate library major version update. Though, for now, we still have major version 0 - so this probably is not necessary.
Anyway, my first request stands. Please put this into another pull request.

@@ -2,6 +2,7 @@ libsuperiormysqlpp (0.3.1) UNRELEASED; urgency=medium

[ Radek Smejdir ]
* Fix ostream operator for null values in Row
* noexcept Statement.close() will not throw MysqlInternalError anymore
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Please mention also, that instead log function will be called and std::terminate will be called.

@majcl majcl merged commit 2549735 into seznam:devel Dec 13, 2017
@smradCZ smradCZ deleted the gcc_6_3_compile_error branch December 13, 2017 11:19
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Incorrect functions called to get error info when mysql_stmt_close fails
2 participants