[lwip-devel] [task #6683] Document lwIPs thread safety requirements

[Simon Goldschmidt]

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

>Just my opinion, but that would be rather gratuitous API breakage

Not just your opinion, I thought about that also. Maybe we could modify api.h
in a way that the raw-API files are no automatically included
(ip.h/raw.h/udp.h/tcp.h), and document that application thread files only
have to include api.h or sockets.h to work. That would also make it more
clear, I think.

My idea is that, for example we could remove the line #include "lwip/raw.h"
from api.h and instead forward-declarate 'struct raw_pcb;'. That way, we can
make the PCBs (which the user should not manipulate when using netconn API)
kind of 'private'... (I'm not really happy with the forward-declaration of
structs, though...)

Same for sockets.h: by moving #include "tcph.h" to sockets.c and including
"inet.h" we could again hide lwip-internals from sockets.h-users.

    _______________________________________________________

Reply to this item at:

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

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