Bringing master branch to 4.2 #202
Merged
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
…ool 'true' or 'false'
Beautification to remove MSVC warning 4800...
Changes for 4.0 support
…ild against both 4.x and 3.x version
This fixes the build against ZMQ 3.2.
Older version of gcc does not support "enum class" declaration. However, there is already a macro to fix this compatibility issue: ZMQPP_COMPARABLE_ENUM. This patch use this macro instead of "enum class"
Fix compilation with gcc < 4.4
Fix the build error created by #64 because of a missing header inclusion
Add move semantic to zmqpp::actor
I've adopted tests from czmq zloop and also used tests for reactor class.
Added myslef.
Add loop class based on czmq zloop
send and receive functions will return false if the socket timeout is set and the operation times out.
Update documentation of socket send / receive
change template method message::extract() to const
* Add wrapper for zmq_proxy_steerable
[Issue #192] Fixed.
New socket options from 4.2.2, 'fixes' for tests using sockets to avoid port reuse
Fixed some minor typos.
Fix minor typos in README.md
Minor change to instructions - add lines to clone zmqpp and cd into the dir
Minor - clone zmqpp
Do not use commas to separate statements
The version number is updated every time, the rest of the .pc file will need to be manually updated when required.
Added pkg-config generation to project, for make only.
As stated in zmq.h, the zmq_msg_t structure must be aligned on the address boundary if sigbus violations are to be avoided on architectures enforcing the pointer alignment.
Flip the order of _msg and _sent in zmq::frame
…as there are lot of bugfixes I've not mentioned
4.2.0 requirements
|
Unless anyone has a good reason why not to do this I'll probably merge it in later today / tomorrow. |
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.
I realise that we default to the develop branch but due to naming conventions it is possible people still use that as the 'release' branch for whatever build system they are using. Keeping it uptodate of tagged releases is probably a sane thing to do.