\# PuTTY's `unwritten design principles'. It has nothing to do with
\# the User Datagram Protocol.
-\define{versionidudp} \versionid $Id$
-
\A{udp} PuTTY hacking guide
This appendix lists a selection of the design principles applying to
\e{don't} care about. In particular, we expect PuTTY to be compiled
on 32-bit architectures \e{or bigger}; so it's safe to assume that
\c{int} is at least 32 bits wide, not just the 16 you are guaranteed
-by ANSI C. Similarly, we assume that the execution character encoding
-is a superset of the printable characters of ASCII, though we don't
-assume the numeric values of control characters, particularly \cw{'\n'}
-and \cw{'\r'}.)
+by ANSI C. Similarly, we assume that the execution character
+encoding is a superset of the printable characters of ASCII, though
+we don't assume the numeric values of control characters,
+particularly \cw{'\\n'} and \cw{'\\r'}. Also, the X forwarding code
+assumes that \c{time_t} has the Unix format and semantics, i.e. an
+integer giving the number of seconds since 1970.)
\H{udp-multi-backend} Multiple backends treated equally