- 21 Aug, 2015 5 commits
-
-
Dominik Charousset authored
Fix a bug in the handling of receive policies and implicitly flush runnables before reading data from the "virtual network buffer".
-
Dominik Charousset authored
-
Dominik Charousset authored
-
Dominik Charousset authored
-
Marian Triebe authored
This prevents false-positives on slow machines.
-
- 20 Aug, 2015 1 commit
-
-
Dominik Charousset authored
-
- 19 Aug, 2015 2 commits
-
-
Dominik Charousset authored
-
Dominik Charousset authored
-
- 18 Aug, 2015 6 commits
-
-
Joseph Noir authored
-
Dominik Charousset authored
-
Dominik Charousset authored
-
Dominik Charousset authored
-
Dominik Charousset authored
-
Dominik Charousset authored
-
- 17 Aug, 2015 16 commits
-
-
Dominik Charousset authored
-
Dominik Charousset authored
-
ufownl authored
-
Dominik Charousset authored
-
Dominik Charousset authored
-
Dominik Charousset authored
-
Dominik Charousset authored
-
Dominik Charousset authored
-
Dominik Charousset authored
-
Dominik Charousset authored
-
Dominik Charousset authored
-
Dominik Charousset authored
-
Dominik Charousset authored
-
Dominik Charousset authored
-
Dominik Charousset authored
Fix `has_name`
-
ufownl authored
Make `has_name` support scalar types.
-
- 09 Aug, 2015 2 commits
-
-
Dominik Charousset authored
-
Matthias Vallentin authored
This used to be CAF_FAIL, but in the process of streamlining the semantics of this macro to be compatible with Boost.Test, we've lost the ability to express a check which is known to fail. The macro CAF_CHECK_FAIL brings back this capability. The suffix _FAIL after CHECK hints that this is a variation of CAF_CHECK.
-
- 08 Aug, 2015 3 commits
-
-
Matthias Vallentin authored
-
Matthias Vallentin authored
Resolves #332.
-
Matthias Vallentin authored
The macro CAF_REQUIRE and CAF_FAIL now both terminate test execution. The only difference between the two is that CAF_REQUIRE takes a condition and CAF_FAIL a termination erro message. This behavior is similar to Boost.Test. Resolves #330.
-
- 06 Aug, 2015 3 commits
-
-
Marian Triebe authored
GCC can compile code which use `thread_local` on OSX, but generates faulty code. The generated code leads to a heap-use-after-free.
-
Joseph Noir authored
-
Dominik Charousset authored
Fix build on MSVC
-
- 05 Aug, 2015 1 commit
-
-
Marian Triebe authored
This commit includes a fix for `accept` of the socket API with MSVC. Examples are now working, but use the `trivial match case`, the `advanced match case` is not available on MSVC due to internal compiler errors. The `thread_local` keyword is used on MSVC and GCC, while Clang does not support it for now. This commit also fixes minor warnings with the MSVC compiler and removes the `pragma comment` for linking libraries with MSVC.
-
- 03 Aug, 2015 1 commit
-
-
Dominik Charousset authored
-