[lwip-devel] [bug #26069] Documentation of tcp_connect() incorrectly describes handling of errors

[Kieran Mansley]

Follow-up Comment #13, bug #26069 (project lwip):

I'm going to change the documentation.

If we were starting from scratch, there's a case for calling
TCP_EVENT_CONNECTED, but changing this would break all the existing users of
the raw API, including the netconn and socket layers included in lwIP, which
is something I want to avoid.

Although it's odd that you wait on TCP_EVENT_CONNECTED for success and
TCP_EVENT_ERR for failure, it would also be odd that you wait on
TCP_EVENT_CONNECTED for connection errors, and TCP_EVENT_ERR for all other
errors.



    _______________________________________________________

Reply to this item at:

  <http://savannah.nongnu.org/bugs/?26069>

_______________________________________________
  Message sent via/by Savannah
  http://savannah.nongnu.org/