[lwip-devel] [task #6933] Review usage of ASSERT and error handling with LWIP_NOASSERT

[Frédéric Bernon]

Follow-up Comment #5, task #6933 (project lwip):

>I like the look of Simon's patch. We get both assertions when there is a
programmer error in a debug build, and robust error returns (rather than just
carrying on blindly) if there is such an error in release code. 

But for code where application programmers check function return codes, it
just add redundant code, and a such code shouldn't stay in a production code.
Perhaps a macro defined in cc.h (or lwipopts.h) can help to handle both cases
(see comment#2).

    _______________________________________________________

Reply to this item at:

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

_______________________________________________
  Message posté via/par Savannah
  http://savannah.nongnu.org/