[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[lwip-devel] [task #6792] Create ASSERTs for DEBUG compile
From: |
Kieran Mansley |
Subject: |
[lwip-devel] [task #6792] Create ASSERTs for DEBUG compile |
Date: |
Mon, 30 Apr 2007 13:56:40 +0000 |
User-agent: |
Opera/8.02 (X11; Linux i686; U; en) |
Follow-up Comment #8, task #6792 (project lwip):
I agree that asserts are always debug. If you're trying to check for errors
in release code, asserts are not the way to do it - you should write an error
handler instead if the error is expected. However, I can see that others
might want them. I therefore propose:
LWIP_ASSERT for the debug variety that causes whatever is running to fail in
a non-graceful manner
LWIP_CHECK for the non-debug variety that gives a warning, but doesn't do the
non-graceful failure.
In a debug build LWIP_CHECK could be compiled to LWIP_ASSERT
_______________________________________________________
Reply to this item at:
<http://savannah.nongnu.org/task/?6792>
_______________________________________________
Message sent via/by Savannah
http://savannah.nongnu.org/
- [lwip-devel] [task #6792] Create ASSERTs for DEBUG compile, Simon Goldschmidt, 2007/04/20
- [lwip-devel] [task #6792] Create ASSERTs for DEBUG compile, Kieran Mansley, 2007/04/23
- [lwip-devel] [task #6792] Create ASSERTs for DEBUG compile, Simon Goldschmidt, 2007/04/27
- [lwip-devel] [task #6792] Create ASSERTs for DEBUG compile, Simon Goldschmidt, 2007/04/29
- [lwip-devel] [task #6792] Create ASSERTs for DEBUG compile, Kieran Mansley, 2007/04/30
- [lwip-devel] [task #6792] Create ASSERTs for DEBUG compile, Jonathan Larmour, 2007/04/30
- [lwip-devel] [task #6792] Create ASSERTs for DEBUG compile, Simon Goldschmidt, 2007/04/30
- [lwip-devel] [task #6792] Create ASSERTs for DEBUG compile, Jonathan Larmour, 2007/04/30
- [lwip-devel] [task #6792] Create ASSERTs for DEBUG compile,
Kieran Mansley <=