[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

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

From: Jonathan Larmour
Subject: [lwip-devel] [task #6792] Create ASSERTs for DEBUG compile
Date: Wed, 23 May 2007 16:37:49 +0000
User-agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv: Gecko/20070223 Fedora/ Firefox/

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:


  Message sent via/by Savannah

reply via email to

[Prev in Thread] Current Thread [Next in Thread]