Minor updates to thanks-for-fixes.md

This includes the sgit tool that will be published on the website (I am
proud even if it was originally only written for me based on a
persistent problem I had over the years) and it also includes rewording
things to hopefully make them clearer and grammatical fixes (or a fix?)
as well.
This commit is contained in:
Cody Boone Ferguson committed 2023-09-22 04:54:32 -07:00
1 parent dc75047627
commit 145a501375
1 file changed
+13 -10
+13 -10
View File
@@ -10,14 +10,16 @@ several thousand changes and important improvements.
We call out the extensive contributions of [Cody Boone
Ferguson](/winners.html#Cody_Boone_Ferguson) who is responsible for many of the
improvements including many, many **very complicated bug fixes** like
improvements including many, many **very complicated bug fixes** such as
[2001/anonymous](2001/anonymous/anonymous.c) and
[2004/burley](2004/burley/burley.c), making entries not require
`-traditional-cpp`, fixing entries to compile with clang, providing alternate
code where useful or necessary, fixing where possible dead links and otherwise
removing them, typo and consistency fixes. Thank you **very much** for your
extensive efforts in helping improve the IOCCC presentation of past IOCCC
winners and making many many past entries work with modern systems!
`-traditional-cpp` (which are very complicated fixes), fixing entries to compile
with clang, providing alternate code where useful or necessary, fixing where
possible dead links and otherwise removing them, typo and consistency fixes and
writing the [sgit tool](https://github.com/xexyl/sgit) that we've published on the
website. Thank you **very much** for your extensive efforts in helping improve
the IOCCC presentation of past IOCCC winners and making many many past entries
work with modern systems!
[Yusuke Endoh](/winners.html#Yusuke_Endoh) supplied a number of
important bug fixes to a number of past IOCCC winners. Some of
@@ -709,7 +711,8 @@ However `EOF` is not required to be `-1` but merely an int < 0 and this program
assumed that `getc()` will return `-1` on EOF or error, not `EOF`. On systems
where `EOF != -1` it could result in an infinite loop.
For an interesting problem that occurred here check the [bugs.md](bugs.md) file.
For an interesting problem that occurred here and what was done to solve it,
check the [bugs.md](bugs.md) file.
## [1994/westley](1994/westley/westley.c) ([README.md](1994/westley/README.md]))
@@ -731,8 +734,8 @@ there is such a thing anyway :-) ).
## [1995/garry](1995/garry/garry.c) ([README.md](1995/garry/README.md]))
Cody fixed this so that it will compile with modern compilers. The problem was a
missing `int` for the `f` variable. He felt it was important that it works
because the layout does indeed look to him like a rat is dropping core,
missing `int` for the `f` variable. He felt it was even more important that it
works because the layout does indeed look to him like a rat is dropping core :-),
something that the judges suggested.
## [1995/makarios](1995/makarios/makarios.c) ([README.md](1995/makarios/README.md))
@@ -1333,7 +1336,7 @@ not do it implicitly (like macOS does).
## [2005/mikeash](2005/mikeash/mikeash.c) ([README.md](2005/mikeash/README.md))
Cody fixed this to work in linux. The problem was an unknown escape sequence,
`\N` which caused a funny compiler error:
`\N`, which caused a funny compiler error:
```c
};n b[2048];int i