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

[Jonathan Larmour]

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

I disagree about NULL pointer checks in a release build. That would be a
programmer error. Unless you are referring to return values from calls to
e.g. mem_malloc

Otherwise, code should be debugged until it works. In most cases in embedded
stuff, if it doesn't work in the field, there's nothing you can do anyway.
What's the point of having an assert in a TV? Or an air conditioning unit?
(Yes those are two examples where customers of ours are using TCP/IP
stacks!). Or even a printer. In the field there's no point - use a watchdog
instead and just reset. Or if it's that important to you, then leave asserts
on in your release build. But for those who write programs that work, these
sorts of checks are a pointless waste of code.


    _______________________________________________________

Reply to this item at:

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

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