[lwip-devel] [task #6969] Review usage of conn->err in netconn layer

[Frédéric Bernon]

Follow-up Comment #13, task #6969 (project lwip):

About "conn->pcb.tcp = NULL;", in err_tcp, I feel that like an error: if the
field is invalided, how could do_delconn do the tcp_close (and indirectly
call tcp_pcb_remove)? Or tcp_pcb_remove is called by the function which call
err_tcp?

But I always think that conn->err is better, since it provide a way to know
why what kind of error we get. More, it's more generic when we have non-tcp
netconn types...


    _______________________________________________________

Reply to this item at:

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

_______________________________________________
  Message posté via/par Savannah
  http://savannah.nongnu.org/