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

[Kieran Mansley]

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

I would argue that asserts are a debug-only tool, and that they should
compile out with no side effects (other than the assertion not being there)
by default, in the same way that the LWIP_DEBUGF  macros do.

In theory, there should be no fatal errors in the release code!  However, in
practice I can see that that won't always be true, but in such situations
people can turn on the debug macros to get the assertions and find out what
the problem is.

    _______________________________________________________

Reply to this item at:

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

_______________________________________________
  Message sent via/by Savannah
  http://savannah.nongnu.org/