You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Change how the condition is evaluated in ER_ASSERT_E
The new method should generate warnings about assignment in assertions, when
compiler settings allow.
Fix atomics in C++
`atomic_int` and `atomic_flag` in C++ are not macros, but typedefs, thus
`#ifndef` check fails and C++ users get this macro defined for
`atomic_int`:
```c++
`#`define atomic_int std::atomic<int>
```
If then somebody tries to use `atomic_int` with a fully qualified name,
i.e. as `std::atomic_int`, they get a cryptic error saying `std in
namespace std does not name a type`.
Simply importing `atomic_int` and `atomic_flag` into a global namespace
fixes the issue, as this means that both uses are legal:
* `atomic_int`, which is what used in Event Router
* `std::atomic_int`, which might be used in other C++ code.