]> asedeno.scripts.mit.edu Git - PuTTY.git/commit
Ronald Landheer-Cieslak points out that the various back ends which
authorSimon Tatham <anakin@pobox.com>
Sat, 22 Dec 2012 09:40:47 +0000 (09:40 +0000)
committerSimon Tatham <anakin@pobox.com>
Sat, 22 Dec 2012 09:40:47 +0000 (09:40 +0000)
commit38b668648aa0f832600f964d7030879d37d9a302
tree74cb45db6cb0e0bb6a70e9e72b26141bcb088473
parent9a7dd918da75fc0d80aa17c447b2728ba8d1173f
Ronald Landheer-Cieslak points out that the various back ends which
treat all socket closures as clean exits (because the protocol doesn't
provide for transferring a process exit code) could usefully at least
treat _socket errors_ as unclean exits. Patch the Telnet, Rlogin and
Raw backends to retain that information and return INT_MAX to the
frontend.

I wasn't sure whether it was better to solve this by modifying each
affected frontend, or each affected backend. I chose the latter, but
neither is really ideal; this is the sort of thing that makes me wish
we had a piece of fixed middleware in between, independent of both
platform and protocol.

[originally from svn r9730]
raw.c
rlogin.c
telnet.c