- 30 Dec, 2016 1 commit
-
-
Luca Boccassi authored
Solution: wrap the event triggering in the DRAFT ifdef as well as the defines. This ensures that the event are returned only if the library was built with DRAFTs enabled. Also update the test case to expect the new events since it uses the catch-all mask. Although the sequence of event is different and this might be considered as an API breakage, using the catch-all ZMQ_EVENT_ALL mask implies that, well, all events are monitored so it's normal that new ones will be added. Users that don't want this kind of behaviour to change can simply monitor only the event that they care about.
-
- 01 May, 2016 1 commit
-
-
hitstergtd authored
Solution: Put them in the right order to quiet Coverity. Found by: Coverity Scan
-
- 28 Jan, 2016 1 commit
-
-
Constantin Rack authored
Solution: update to 2016
-
- 28 Jul, 2015 1 commit
-
-
Brian Silverman authored
I'm pretty sure this is an issue with the test being too picky and not a bug, but the behavior in this situation is not well documented.
-
- 02 Jun, 2015 1 commit
-
-
Pieter Hintjens authored
Of course people still "can" distributed the sources under the LGPLv3. However we provide COPYING.LESSER with additional grants. Solution: specify these grants in the header of each source file.
-
- 22 Jan, 2015 1 commit
-
-
Pieter Hintjens authored
Solution: update for 2015 Fixes #1320
-
- 28 Apr, 2014 1 commit
-
-
Pieter Hintjens authored
Specifically: * zmq_event_t should not be used internally in libzmq, it was meant to be an outward facing structure. * In 4.x, zmq_event_t does not correspond to monitor events, so I removed the structure entirely. * man page for zmq_socket_monitor is incomplete and the example code was particularly nasty. * test_monitor.cpp needed rewriting, it was not clean.
-
- 02 Jan, 2014 1 commit
-
-
Pieter Hintjens authored
-
- 06 Nov, 2013 1 commit
-
-
Pieter Hintjens authored
- used msleep (10) in most places instead of zmq_sleep (1) - may cause failures on slower machines - to change, modify SETTLE_TIME in testutil.h - tested down to 1 msec on fast boxes
-
- 15 Sep, 2013 1 commit
-
-
Pieter Hintjens authored
* Removed redundant Z85 code and include files from project * Simplified use of headers in test cases (now they all just use testutil.hpp) * Export zmq_z85_encode() and zmq_z85_decode() in API * Added man pages for these two functions
-
- 17 Aug, 2013 2 commits
-
-
Richard Newton authored
-
Richard Newton authored
-
- 01 Jul, 2013 2 commits
-
-
Richard Newton authored
-
Richard Newton authored
-
- 22 Jun, 2013 2 commits
-
-
Pieter Hintjens authored
-
Ian Barber authored
Also tidy up monitor test a little.
-
- 12 Mar, 2013 1 commit
-
-
Pieter Hintjens authored
-
- 08 Mar, 2013 2 commits
-
-
Guido Goldstein authored
-
Guido Goldstein authored
Simplified the zmq_event_t structure for easier access and better usability towards language bindings.
-
- 31 Jan, 2013 2 commits
-
-
Pieter Hintjens authored
* Removed or truncated sleeps so the tests run faster * Removed dependencies on zmq_utils * Rewrote a few tests that were confusing * Minor code cleanups
-
Pieter Hintjens authored
-
- 21 Sep, 2012 1 commit
-
-
Lourens Naudé authored
Significantly reworked the monitoring infrastructure with a more granular per socket API and to play well with monitoring endpoints in application threads
-
- 06 Sep, 2012 1 commit
-
-
Arthur O'Dwyer authored
This change makes sure that even if the tests are built in a "release" configuration (with optimizations and NDEBUG turned on), the assertions won't get compiled out of the tests themselves. The C standard guarantees that the most recent inclusion of <assert.h> is the one that counts, so it's important that the "#undef NDEBUG/#include <assert.h>" come as the last thing in the block of header files. "testutil.hpp" includes <assert.h>, so I've left <assert.h> out of any test that #includes "testutil.hpp", just for the sake of brevity.
-
- 27 Aug, 2012 1 commit
-
-
Arthur O'Dwyer authored
This formerly unused parameter actually represents the socket on which the event was received. As such, we should check that its value makes sense: it must be either "rep" or "req", and in the case of some kinds of events, it must be specifically one or the other. After this change, "s" is no longer unused.
-
- 23 Aug, 2012 1 commit
-
-
Arthur O'Dwyer authored
Both memcmp and strcmp return zero on equal, nonzero on nonequal; so all of these tests were backwards. The original committer fixed the failure by comparing 22 bytes instead of the correct 21, so that the assertions would trigger only if the 22nd byte happened to match exactly --- which was rare. The correct fix is to compare the right number of bytes with the right sense. (I think all of the ".addr" fields are null-terminated, in which case it's more appropriate to use strcmp throughout.)
-
- 04 Aug, 2012 1 commit
-
-
Lourens Naudé authored
-
- 05 Jun, 2012 1 commit
-
-
AJ Lewis authored
GCC 4.1.2 on RHEL5 and SLES10 don't like not having a newline at the end of a source file, and error out if it's missing. Signed-off-by:
AJ Lewis <aj.lewis@quantum.com>
-
- 22 May, 2012 1 commit
-
-
Lourens Naudé authored
-
- 21 May, 2012 1 commit
-
-
Lourens Naudé authored
-
- 20 May, 2012 2 commits
-
-
Lourens Naudé authored
Rename type zmq_monitor_fn -> zmq_monitor for a more natural callback definition API (zmq_monitor type, monitor.function callback)
-
Lourens Naudé authored
Change zmq_monitor_fn type to cast between pointer-to-object and pointer-to-function in a more standards compliant way
-
- 13 May, 2012 1 commit
-
-
KennyTM~ authored
The current ZMQ_MONITOR code does not compile in gcc 4.7, as -pedantic and -Werror are enabled, and ISO C++ doesn't allow casting between normal pointers (void*) and function pointers, as pedantically their size could be different. This caused the library not compilable. This commit workaround the problem by introducing one more indirection, i.e. instead of calling (void *)listener which is an error, we have to use *(void **)&listener which is an undefined behavior :) but works on most platforms Also, `optval_ = monitor` will not set the parameter in getsockopt(), and the extra casting caused the LHS to be an rvalue which again makes the code not compilable. The proper way is to pass a pointer of function pointer and assign with indirection, i.e. `*optval_ = monitor`. Also, fixed an asciidoc error in zmq_getsockopt.txt because the `~~~~` is too long.
-
- 04 May, 2012 1 commit
-
-
Lourens Naudé authored
-