From 1f8b3b5535176f413c0af11b1d4c6912670b0bdc Mon Sep 17 00:00:00 2001 From: Simon Tatham Date: Sat, 26 Dec 2020 15:40:04 +0000 Subject: [PATCH] Update docs section about use of global variables. It referred to the global variable 'flags' as an example. But 'flags' was retired (and good riddance) nearly a year ago, in commit 4ea811a0bf. So we should be using a different example now! --- doc/udp.but | 11 +++++------ 1 file changed, 5 insertions(+), 6 deletions(-) diff --git a/doc/udp.but b/doc/udp.but index 406b469f..12e29f78 100644 --- a/doc/udp.but +++ b/doc/udp.but @@ -142,12 +142,11 @@ potentially managing multiple sessions. Therefore, the platform-independent parts of PuTTY never use global variables to store per-session data. The global variables that do exist are tolerated because they are not specific to a particular -login session: \c{flags} defines properties that are expected to -apply equally to \e{all} the sessions run by a single PuTTY process, -the random number state in \cw{sshrand.c} and the timer list in -\cw{timing.c} serve all sessions equally, and so on. But most data -is specific to a particular network session, and is therefore stored -in dynamically allocated data structures, and pointers to these +login session. The random number state in \cw{sshrand.c}, the timer +list in \cw{timing.c} and the queue of top-level callbacks in +\cw{callback.c} serve all sessions equally. But most data is specific +to a particular network session, and is therefore stored in +dynamically allocated data structures, and pointers to these structures are passed around between functions. Platform-specific code can reverse this decision if it likes. The