summaryrefslogtreecommitdiffstats
path: root/arithmetic
diff options
context:
space:
mode:
authorhubertf <hubertf@NetBSD.org>1999-07-16 01:38:20 +0000
committerhubertf <hubertf@NetBSD.org>1999-07-16 01:38:20 +0000
commitae9b67f6a8d26e5428a3cbefadaa66889d4c9137 (patch)
treeaf3201abc93c14ff6a072d9986c768e94c511de8 /arithmetic
parentda4e0287800b9ed4057f3ba8624f9d697719e6f9 (diff)
downloadbsdgames-darwin-ae9b67f6a8d26e5428a3cbefadaa66889d4c9137.tar.gz
bsdgames-darwin-ae9b67f6a8d26e5428a3cbefadaa66889d4c9137.tar.zst
bsdgames-darwin-ae9b67f6a8d26e5428a3cbefadaa66889d4c9137.zip
This patch cleans up the handling of the variable `saved' in
adventure(6). The handling of this variable is somewhat confusing, since it is used for two different purposes (controlling the time required before a saved game can be restored, and controlling various aspects of dwarf behaviour); in fact, it is also declared twice in hdr.h. Except possibly when saving a game fails, these uses can never interfere; when used for controlling dwarf behaviour, we always have saved == -1. This can be better understood with reference to the original PDP-10 FORTRAN source (URL in patch, since hdr.h references the comments of the FORTRAN as still relevant to this version) of which the C version is a direct translation: the wrong value for `saved' meant that someone was cheating and had bypassed normal initialisation. Saving was done by halting and telling the user to save their core image, so the question of carrying on after saving failed to open the output file did not arise. This patch separates the uses of `saved' into uses of two separate variables. Closes PR 8005 by Joseph Myers <jsm28@cam.ac.uk>
Diffstat (limited to 'arithmetic')
0 files changed, 0 insertions, 0 deletions