summaryrefslogtreecommitdiff
path: root/src
diff options
context:
space:
mode:
authorBardur Arantsson <bardur@scientician.net>2017-06-13 18:24:42 +0200
committerBardur Arantsson <bardur@scientician.net>2017-06-13 18:24:42 +0200
commit0595b2fa946619d29624505f8edc0f9c00146e61 (patch)
tree3451136cacfad903b7614b295edb0379b8a8c04c /src
parent87a6c654d3f83837319f7459c07bd2c31d70fa63 (diff)
Remove pointless comment
Diffstat (limited to 'src')
-rw-r--r--src/loadsave.cc14
1 files changed, 1 insertions, 13 deletions
diff --git a/src/loadsave.cc b/src/loadsave.cc
index dacd0e15..a085283d 100644
--- a/src/loadsave.cc
+++ b/src/loadsave.cc
@@ -66,20 +66,8 @@ struct option_value {
/*
- * Basic byte-level reading from savefile. This provides a single point
- * of interface to the pseudoencryption that ToME (and Angband)
- * uses. I'm thinking about if it might be faster/better to modify all
- * the do_* functions to directly do this stuff -- it'd make the code
- * somewhat uglier to maintain, but concievably might be much faster. Or
- * is it better maybe to scrap the pseudoencryption entirely and adopt
- * some other means of obfuscation, should it still prove useful in any
- * way? -- Improv
- *
- * What's the point of encryption on savefiles anyway? If I wanted to
- * make a cheater savefile, I'd activate debug mode, and hack the game
- * not to save it. There's no point. -- takkaria
+ * Basic byte-level reading from savefile.
*/
-
static byte sf_get()
{
byte c;