I noted in bugs.md that there is a bug that remains and I noted the bug
in the README.md too (under the to run section) as it seems like it
should be noted (sometimes the program needs you to press return to
continue solving the maze).
Some entries were added to the bugs.md file.
As well some README.md files were updated wrt the bugs some of which
might have been better in an earlier commit.
Fixing these would actually cause problems. This includes one I fixed
where an incompatible pointer type was introduced. This was necessary to
make it work. I experimented with the other options and it did not work
at all.
Added another section: entries that require -traditional-cpp support.
Also finished an unfinished sentence that was put in (another one was
ironically fixed in the previous commit).
I have added sections as not all problems are the same. Some are not
supposed to be touched for instance and others have partial fixes. Some
will work with some compilers but not others. There is one entry (for
now) where things might appear to be bugs but are not (2020/ferguson1).
I added links to each entry along with the README.md file.
I have given tips to the problems in some cases.
Yes some of the entries refer to me and one entry even has a tip related
to the entry I worked on (2020/ferguson2) that helped me discover the
bug as using the Enigma machine can help identify problems (I gave
an example in the README.md file which I also linked to).
The rationale is that it'll become a html file on the main site and
having www.ioccc.org/BUGS.html seems less ideal than
www.ioccc.org/bugs.html though I suppose this is only subjectively
better esp as many distributions of software have a BUGS file (and in
fact I had such a file in 2020/ferguson1 but now it's lower case). Still
this can be debated later I suppose.
Cody Boone Ferguson