On Thu, Nov 21, 2019 at 12:17 AM Petr Štetiar wrote:
> Michael Jones [2019-11-20 18:12:14]:
>
> > You may need #include_next, to avoid recursion.
>
> Is this some theoretical experience? Or you can provide me with some build
> breakage? Just wondering, because #include should work this out with
Michael Jones [2019-11-20 18:12:14]:
> You may need #include_next, to avoid recursion.
Is this some theoretical experience? Or you can provide me with some build
breakage? Just wondering, because #include should work this out with "" and
<>.
BTW I would rather rename that include file to assert
You may need #include_next, to avoid recursion.
On Wed, Nov 20, 2019, 15:45 Petr Štetiar wrote:
> In order to allow seamless assert() usage in release builds without the
> need for fiddling with CMake C flags as CMake adds -DNDEBUG switch in
> release builds which disable assert().
>
> Signed-of
In order to allow seamless assert() usage in release builds without the
need for fiddling with CMake C flags as CMake adds -DNDEBUG switch in
release builds which disable assert().
Signed-off-by: Petr Štetiar
---
assert.h | 9 +
1 file changed, 9 insertions(+)
create mode 100644 assert.
