[lwip-devel] [task #6792] Create ASSERTs for DEBUG compile

[Simon Goldschmidt]

Follow-up Comment #6, task #6792 (project lwip):

I wanted to introduce LWIP_DEBUG_ASSERT() to have an easy way of adding extra
checks when developing which should normally not fire. This could be an
lwIP-newbie for example, who needs some extra-checks.

Or a developer like me, who wants to make sure the code works using some
ASSERTs not really needed after the code works. In this case,  I think having
DEBUG-ASSERTs is better than using normal ASSERTs and removing them later, as
you have kind of documentation of the original programmer's idea/checks in
the code. I think that alone is worth a lot looking at some of the
discussions we had throughout the last months.

On the other hand, I think it sometimes is easier to run into an ASSERT
(which for me, automatically reboots the system through a watchdog) than
including code for all kind of failures. So I think there should be a
distiction between normal ASSERTs (triggering on errors that can happen
during normal running of an application) and DEBUG-ASSERTs (triggering if you
use the stack in a wrong way). The latter can be turned off once you know your
code/configuration is OK.

    _______________________________________________________

Reply to this item at:

  <http://savannah.nongnu.org/task/?6792>

_______________________________________________
  Nachricht geschickt von/durch Savannah
  http://savannah.nongnu.org/