-
Notifications
You must be signed in to change notification settings - Fork 2.2k
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
Mark deprecated functionality with C++ attributes and resolve internal usage of deprecated functions #4551
Conversation
f2c5384
to
bc4b50a
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I am not sure if @deprecated
is needed/used by PocoDoc
, @obiltschnig would know
bc4b50a
to
3999dcd
Compare
f63afd3
to
da8037a
Compare
da8037a
to
fe5f2b5
Compare
Functionality that was marked as deprecated with comments is now marked as such with C++ attribute with a few exceptions:
Usage of deprecated functions and classes in Poco code is replaced with non-deprecated variants. Unit tests for deprecated functionality are disabled by default and can be enabled with Some C++ code modernisation was done in the code while resolving deprecations. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Overall looks good, than you. I'm just thinking it would be good to have a single place to disarm warnings somehow.
@@ -235,6 +232,7 @@ void SQLChannel::run() | |||
{ | |||
try | |||
{ | |||
sleepTime = 100; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
warning: likely to cause merge conflict with #4530
Do you mean deprecation warnings that will be seen by the users of Poco? Do we want to disarm them? |
I foresee some annoyance if we swamp the build with deprecation warnings. In any case, I think there should be an easy way to disable them. |
105597b
to
ad8c34f
Compare
Introduced a macro IMO the branch is ready to be merged to main. @obiltschnig, @aleks-f, any objections? |
…lve internal usage of deprecated functions (#4551) * enh(poco): Replace deprecated comments with C++ deprecated attribute. * enh(Poco): Replace some deprecated functionality in Poco sources. (#4426) * enh(Poco): Replace more deprecated functionality in Poco sources. (#4426) * fix(CMake): Variable BUILD_SHARED_LIBS must be defined properly to create valid binaries. * enh: Code improvements done while resolving deprecated functionality (#4426) * Un-deprecate LocalDateTme (#4426) * enh(Poco): Replace usage of deprecated functionality with other functions/classes (#4426) * chore(SSL): temporarily un-deprecate SSL-related functionality (#4426) * chore(SSL): temporarily un-deprecate old MongoDB protocol functionality (#4426) * enh(Poco): Minor Hash improvements (#4426) * enh(Foundation): Compile deprecated hash tests only when POCO_TEST_DEPRECATED is enabled (#4426) * enh(Net): Compile deprecated Socket::select functionality only when POCO_TEST_DEPRECATED is enabled (#4426) * enh(Bonjour): Replace deprecated Socket::select with PollSet (#4426) * enh(Poco): Introduce POCO_DEPRECATED macro to have the ability to disable deprecation warnings in applications (#4426) * test(ODBC): add few asserts to testStoredProcedureDynamicVar * fix(ODBC): rename DynamicAny -> DynamicVar in tests * fix(ODBC): make Dignostics static members inline to prevent explicit instantiation warnings on windows --------- Co-authored-by: Alex Fabijanic <alex@pocoproject.org>
Closes #4426.