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

[Simon Goldschmidt]

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

                 Summary: Create ASSERTs for DEBUG compile
                 Project: lwIP - A Lightweight TCP/IP stack
            Submitted by: goldsimon
            Submitted on: Freitag 20.04.2007 um 19:06
                Category: None
         Should Start On: Freitag 20.04.2007 um 00:00
   Should be Finished on: Freitag 20.04.2007 um 00:00
                Priority: 1 - Later
                  Status: None
                 Privacy: Public
        Percent Complete: 0%
             Assigned to: None
             Open/Closed: Open
         Discussion Lock: Any
                  Effort: 0.00

    _______________________________________________________

Details:

I've read on a different thread that we don't take much care in checking
application error conditions (wrong arguments etc.)?
This probably comes from fear of performance loss, which I can understand.
This could make porting / learning lwIP a hard time.

As a solution, I propose to add a new assert macro, LWIP_DEBUG_ASSERT() that
only executes if LWIP_DEBUG is defined. That way we can avoid performance
loss due to error checking and still can discover misbehaviour (mostly of the
programmer) during creation/debugging phase. Currently, we can only turn on or
off all asserts together and can't decide between critical and
programmer-fault asserts.




    _______________________________________________________

Reply to this item at:

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

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