[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: Simon Goldschmidt
Subject: [lwip-devel] [task #6792] Create ASSERTs for DEBUG compile
Date: Wed, 23 May 2007 15:05:44 +0000
User-agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; de; rv: Gecko/20070309 Firefox/

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

>Or asking it another way, would LWIP_CHECK be checking for things that
really can go wrong sometimes, or only go wrong if there's a bug in lwIP? It
seems to me that the former is better handled with error returns. So I guess
you mean the latter?

I'd also like to disable both to have faster code in a bug-free lwIP stack
;-) But maybe it is better to have some checks all the time...

And if you mean LWIP_CHECK should fire for a bug in lwip, I'd call it
LWIP_FATAL. I don't really understand the meaning of LWIP_CHECK. If it's a
non-fatal check, why include it in a release build?


Reply to this item at:


  Nachricht geschickt von/durch Savannah

reply via email to

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