From 9e2b5696611ead8e030fc86e81d1e7c3031f0067 Mon Sep 17 00:00:00 2001
From: Cody Boone Ferguson <53008573+xexyl@users.noreply.github.com>
Date: Sun, 10 Sep 2023 09:58:27 -0700
Subject: [PATCH] Update FAQ about incongruent code & author remarks

As I was looking at 2004/burley/README.md it occurred to me that
numerous entries have been modified in ways that are incongruent with
what the author(s) originally wrote about the entry. In some cases this
has been noted in the README.md file (like has been added to
2004/burley/README.md itself) but not in all. That should probably be
checked for and I will do that in time most likely but in the meantime
it felt even better to update the FAQ about this which this commit does
as well.
---
 2004/burley/README.md |  3 +++
 faq.md                | 17 ++++++++++++++---
 2 files changed, 17 insertions(+), 3 deletions(-)

diff --git a/2004/burley/README.md b/2004/burley/README.md
index 10cd44930..f86870a62 100644
--- a/2004/burley/README.md
+++ b/2004/burley/README.md
@@ -70,6 +70,9 @@ the program so this "strategy" no longer works?
 Notice the clever use of `setjmp()` and `longjmp()` calls.  Can you keep track
 of what state is being saved and restored?
 
+NOTE: the author talks about how it is a single statement. This might not be
+strictly true in 2023 for the fixes for it to work so you can look at the
+original file [burley.orig.c](burley.orig.c) to see what is meant.
 
 ## Author's remarks:
 
diff --git a/faq.md b/faq.md
index 3a9d2e318..d43197cd2 100644
--- a/faq.md
+++ b/faq.md
@@ -33,6 +33,14 @@ By tradition, we do not say.
 ## Q: How many judging rounds do you have?
 Are you trying to trick us? We will not say that either.
 
+## Q: How come some entries have code that is incongruent with what the author(s) wrote about the entry?
+
+It is very likely in this case that the code was fixed to work for modern
+systems as part of the reworking of the website. If you have this problem in
+some entries you should look at the original code as in `winner.orig.c` or
+`prog.orig.c`. Sometimes the original is in an alt version like `winner.alt.c`
+or `prog.alt.c`.
+
 ## Q: I cannot get entry XYZZY from year 19xx to compile!
 
 Some winners, particularly winners from long ago, no longer compile on more
@@ -64,9 +72,12 @@ Mill](/winners.html#Christopher_Mills)'s entry
 PDP-11/40 emulator. 
 
 Others are not so easy though we're working on this and over time have added
-alternative code. Most entries do now work and the others we are working on. In
-some cases we replaced the original code with code that works for modern systems
-but one can view the original code in the `.orig.c` files (sometimes the
+alternative code and/or fixed them. Most entries do now work and the others we
+are working on (slowly as other things are also being done and this is on free
+time).
+
+In some cases we replaced the original code with code that works for modern
+systems but one can view the original code in the `.orig.c` files (sometimes the
 original code is also in the directory as a `winner.alt.c` or `prog.alt.c`).
 
 ## Q: After running a program my terminal is all messed up! How do I restore my terminal?