1984/index.html, scroll down to Winning Entries of
Jump to: top
-Q 8.0: How can I find out what was changed in an IOCCC entry source code?
+Q 8.0: What was changed in some IOCCC entries?
+When the website was being worked on in 2022-2024, the hint files were changed
+to README.md, which are now used to construct index.html files, most text was
+converted to markdown, typos were fixed, formatting fixes were made and most
+entries that no longer worked were fixed to work or partly work.
+If you wish to find out more, and see how to see the actual differences, check
+the
+FAQ on “how to find extended details of what was changed”.
+
+Q 8.0.1: How can I see the extended details of what was changed?
+
We have set up make rules to easily do see what was changed in the winning IOCCC
entry source. Using the Makefile in the entry directory, use
one of the following make(1) rules:
@@ -4036,6 +4047,9 @@ include Makefile via the optional include directive line:
The 1337.mk file must exist in the current
directory, or under the directory above, or under the directory 2 levels
above in order for these rules to work.
+If you’re an IOCCC masochist :-), or you really want even more details, very often the
+thanks file has much more details on what had to be
+changed.
Tip: if you have colordiff installed it’s a lot easier to see the differences
To use these rules but provide a different diff, for instance colordiff,
just do:
@@ -4044,7 +4058,7 @@ just do:
Obviously if you want to view the alternate code or the orig code you can just open
the files as described above.
See the
-FAQ on “original source code”
+FAQ on “original source code files”
for more information.
Jump to: top
@@ -4225,7 +4239,9 @@ the source code as it is now now, try:
make diff_orig_prog
See the
FAQ on “what changed”
-for more information and make rules relating to “original source file” differences.
+for more information on changes. If you want to see more details, including how
+to see the actual differences, see the
+FAQ on “what changed in more detail”.
Jump to: top
Q 8.8: Why were some filenames changed?
diff --git a/faq.md b/faq.md
index 68d1ac777..8604ab389 100644
--- a/faq.md
+++ b/faq.md
@@ -87,7 +87,8 @@ This is FAQ version **28.1.2 2024-10-21**.
## 8. [Changes made to IOCCC entries](#changes)
-- **Q 8.0**: How can I find out what was changed in an IOCCC entry source code?
+- **Q 8.0**: What was changed in some IOCCC entries?
+- **Q 8.0.1**: How can I see the extended details of what was changed?
- **Q 8.1**: Why were some calls to the libc function gets(3) changed to use fgets(3)?
- **Q 8.2**: Why do some remarks seem inconsistent with the entry?
- **Q 8.3**: What is the meaning of the file ending in .orig.c in IOCCC entries?
@@ -4822,10 +4823,23 @@ Jump to: [top](#)
-### Q 8.0: How can I find out what was changed in an IOCCC entry source code?
+### Q 8.0: What was changed in some IOCCC entries?
+When the website was being worked on in 2022-2024, the hint files were changed
+to README.md, which are now used to construct index.html files, most text was
+converted to markdown, typos were fixed, formatting fixes were made and most
+entries that no longer worked were fixed to work or partly work.
+
+If you wish to find out more, and see how to see the actual differences, check
+the
+FAQ on "[how to find extended details of what was changed](#detailed-diff)".
+
+
+### Q 8.0.1: How can I see the extended details of what was changed?
+
+
We have set up make rules to easily do see what was changed in the winning IOCCC
entry source. Using the `Makefile` in the entry directory, use
one of the following `make(1)` rules:
@@ -4852,6 +4866,7 @@ The following `make` rules exist to make a difference:
- This rule will show the diff of the entry to the original code (that is
`entry.c` to `entry.orig.c`).
+
For instance one of Landon's all time favourite entries is
[1984/mullender](1984/mullender/index.html) so the file names would be:
`mullender.orig.c`, `mullender.alt.c` and `mullender.c`. For later years, it
@@ -4917,6 +4932,10 @@ The [1337.mk](%%REPO_URL%%/1337.mk) file must exist in the current
directory, or under the directory above, or under the directory 2 levels
above in order for these rules to work.
+If you're an IOCCC masochist :-), or you really want even more details, very often the
+[thanks file](thanks-for-help.html) has much more details on what had to be
+changed.
+
#### Tip: if you have `colordiff` installed it's a lot easier to see the differences
@@ -4932,7 +4951,7 @@ Obviously if you want to view the alternate code or the orig code you can just o
the files as described above.
See the
-FAQ on "[original source code](#original_source_code)"
+FAQ on "[original source code files](#original_source_code)"
for more information.
Jump to: [top](#)
@@ -5176,7 +5195,9 @@ the source code as it is now now, try:
See the
FAQ on "[what changed](#what_changed)"
-for more information and make rules relating to "**original source file**" differences.
+for more information on changes. If you want to see more details, including how
+to see the actual differences, see the
+FAQ on "[what changed in more detail](#detailed-diff)".
Jump to: [top](#)
diff --git a/thanks-for-help.html b/thanks-for-help.html
index f6fc58afb..e0304dba2 100644
--- a/thanks-for-help.html
+++ b/thanks-for-help.html
@@ -409,6 +409,7 @@ on an IOCCC entry by entry basis.
- Makefiles fixes and improvements
- Consistency improvements
- Manifest improvements
+- FAQ improvements
- Thank you honor roll
- Did we neglect to credit you?
@@ -4743,6 +4744,11 @@ manually.
Cody greatly improved the manifest of the winning entries so that the
links to the files in the index.html files make sense and are consistent,
although some might not make as much sense unless one looks into the entry.
+
+FAQ improvements
+
+Cody greatly extended the FAQ to include much more information and he
+helped reorganise it as well, from the new faq.md file.
Thank you honor roll
@@ -4792,10 +4798,11 @@ Wayback Machine replace bad, broken, or otherwise
invalid links are thanks to Cody’s efforts! Another tool he wrote detected
inconsistent award titles in the README.md files (used to generate the
index.html files) and the CSV file that he generated from our SQL file.
-Additionally Cody greatly improved the manifest of the winning entries and
-checked that the generated html files, index.html and otherwise, look well and
-are presentable, and he also suggested some CSS rules for image responsiveness on smaller
-screens, as well as some other improvements.
+Cody also greatly improved the manifests and checked that the generated html
+files look well and are presentable, and he also suggested some CSS rules for
+image responsiveness on smaller screens, as well as some other improvements.
+Cody also wrote some of the website scripts and improved and
+bug fixed others.
THANK YOU VERY MUCH for your extensive efforts in helping improve the IOCCC
presentation of past IOCCC entries and fixing almost all past entries for modern
systems!
diff --git a/thanks-for-help.md b/thanks-for-help.md
index 422d328d4..be20d89c8 100644
--- a/thanks-for-help.md
+++ b/thanks-for-help.md
@@ -25,6 +25,7 @@ on an IOCCC entry by entry basis.
- [Makefiles fixes and improvements](#makefiles_fixes_improvements)
- [Consistency improvements](#consistency_improvements)
- [Manifest improvements](#manifest_improvements)
+- [FAQ improvements](#faq_improvements)
- [Thank you honor roll](#thank_you_honor_roll)
- [Did we neglect to credit you?](#neglect)
@@ -6171,6 +6172,13 @@ manually.
links to the files in the index.html files make sense and are consistent,
although some might not make as much sense unless one looks into the entry.
+
+## FAQ improvements
+
+
+[Cody](#cody) greatly extended the FAQ to include much more information and he
+helped reorganise it as well, from the new `faq.md` file.
+
## Thank you honor roll
@@ -6233,10 +6241,12 @@ invalid links are thanks to Cody's efforts! Another tool he wrote detected
inconsistent award titles in the `README.md` files (used to generate the
`index.html` files) and the CSV file that he generated from our SQL file.
-Additionally Cody greatly improved the manifest of the winning entries and
-checked that the generated html files, `index.html` and otherwise, look well and
-are presentable, and he also suggested some CSS rules for image responsiveness on smaller
-screens, as well as some other improvements.
+Cody also greatly improved the manifests and checked that the generated html
+files look well and are presentable, and he also suggested some CSS rules for
+image responsiveness on smaller screens, as well as some other improvements.
+
+Cody also wrote some of the [website scripts](bin/index.html) and improved and
+bug fixed others.
**THANK YOU VERY MUCH** for your extensive efforts in helping improve the IOCCC
presentation of past IOCCC entries and fixing almost all past entries for modern