[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: |
Jonathan Larmour |
Subject: |
[lwip-devel] [task #6792] Create ASSERTs for DEBUG compile |
Date: |
Mon, 30 Apr 2007 13:48:27 +0000 |
User-agent: |
Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.8.0.10) Gecko/20070223 Fedora/1.5.0.10-1.fc5 Firefox/1.5.0.10 |
Follow-up Comment #7, task #6792 (project lwip):
I think I see what you're getting at. Perhaps there might be a clearer way to
put this in the name - for me asserts are always a "debug" thing, so having
one be LWIP_ASSERT and another LWIP_DEBUG_ASSERT doesn't offer much
difference.
Just a suggestion, but perhaps there could be other names like
LWIP_APP_ASSERT, LWIP_USER_ASSERT, LWIP_API_ASSERT?
Anyway, thanks for the explanation. Perhaps there's some file (or in a
comment in opt.h) a summary of this could go into?
_______________________________________________________
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 <=
- [lwip-devel] [task #6792] Create ASSERTs for DEBUG compile, Kieran Mansley, 2007/04/30