[Top][All Lists]

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

[lwip-devel] [task #6935] Problems to be solved with the current socket/

From: Frédéric Bernon
Subject: [lwip-devel] [task #6935] Problems to be solved with the current socket/netconn API
Date: Thu, 24 May 2007 15:12:43 +0000
User-agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; fr; rv: Gecko/20070309 Firefox/

Follow-up Comment #8, task #6935 (project lwip):

About comment#6:

>Function-like macros could be used to control it so that we don't have a
mess of ifdefs - depending on the user's chosen options, some will evaluate
to nothing. So for example, on entry to an API function, something like
LOCK_CONNECTION(conn) would be called, which in some configurations would
actually lock the whole stack, not just the connection. 

Jonathan, is the idea to avoid #if/#else/#endif ? If right, can you give me
your opinion about https://savannah.nongnu.org/patch/?5959, comment#2 ?


Reply to this item at:


  Message posté via/par Savannah

reply via email to

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