C++17 compliance #592
Closed
C++17 compliance #592
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
zaphoyd
pushed a commit
that referenced
this pull request
Jun 11, 2017
|
I've applied most of this patch to the develop branch. I am leaving in the use of auto_ptr when compiling in pre-c++11 environments only. I believe this should be sufficient to allow C++17 compiling |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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 new c++ 17 standard removes std::auto_ptr and std::binary_function.
websocketpp contains them in memory.hpp and utilities.hpp respectively.
websocketpp cannot be compiled with those anymore on the latest VS"15".