On 17 Apr 2018, at 9:13pm, Peter Da Silva <peter.dasi...@flightaware.com> wrote:
> Even on Windows, wouldn't doing an ssl_shutdown on a socket you'd already > closed still have a risk of unexpected behavior? Under Windows an attempting to shutdown a connection which is already shutdown returns SOCKET_ERROR . You can then make further calls to learn that the exact problem was an attempt to close something that isn't an open socket. The major problem is analogous to one with SQLite: most software doesn't check the return value because if the return value is not 0 there's nothing simple that can be done about it. It's simpler, and 99% of the time perfectly okay, to just quit as if no error had occurred. Simon. _______________________________________________ sqlite-users mailing list sqlite-users@mailinglists.sqlite.org http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users
