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

[Simon Goldschmidt]

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

>Or with LWIP_ASSERT becoming just a warning in a release build.

If LWIP_ASSERT becomes a check in release, there still has to be error
handling code. So we can leave away the assert completely (to be faster) and
the user simply has to check the return values...

By now, I don't think that it's necessary to have release-asserts, since we
decided to write the code in a way that errors are handled by returning error
values.

Only the decision is not that easy. I think that e.g. NULL-pointer checks
should be checked in a release build also.

    _______________________________________________________

Reply to this item at:

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

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