A strange problem is that although it worked with macOS and linux for me
numerous times in the past it stopped working under both. I went to try
and figure it out but when disabling the optimiser for debug symbols the
problem vanished. Changing it back to -O3 and the problem reappeared
both with macOS and linux. Thus it appears that the entry should not
have -O level > 0. I'm not sure if this is the same issue the author
reported where it sometimes segfaults but I did not try and figure it
out either (in any event the crash disappeared when -O0 was specified so
it'd be harder to debug).
Added to .gitignore the file the author noted the program is called (as
the command he gives creates). To make it easier I just made it a
symlink to prog.
Fixed formatting in README.md.
There were many many README.md files with the wrong heading level for
different sections. These have been changed.
To help go through the changes it should be noted I used sgit and also
here is what is changed:
The 'Try', 'To build' and 'To run' lines have two '#'s. Some had one and
others had three.
An exception is that in 1984/anonymous/README.md for the alternative
code that had three '#'s. This is not consistent yet and it might be
that only two are desired. But for now that one at least has three.
Simply the Makefile header.
Refer to the //www.ioccc.org/bugs.md URL (that will eventually exist).
Now using CC BY-SA 4.0 License to how you may share and adapt the
Makefile.
In at least one case some -D flags had to be added to the Makefile.
Typo fixes and formatting fixes in some README.md files.
For the simply amazing 2019/karns I added a demo.sh which does a cat on
the two files (prog.c and maze) and then sleeps for two seconds then
runs the program then sleeps for two seconds then resets the terminal
(so the colours are messed up). This was added to the README.md file.
Several .gitignore files were added.
I'm aware that the graphics editing one does not now work under macOS
but I'm not sure if this is all versions so I just noted that it doesn't
seem to work with recent versions of macOS as I don't have a way to test
before Ventura (the current version).
The commit 00ae59cd47 had a
mistake that introduces changes to Makefiles for 1996 thru 2020
that should not have been included.
This change reverses these intermediate changes until
the given year's Makefiles are ready.
In particular the following fixes were made:
-MKFIFo= mkfifo
+MKFIFO= mkfifo
-ZIPGREp= zipgrep
-ZIPINFo= zipinfo
+ZIPGREP= zipgrep
+ZIPINFO= zipinfo
If it's not immediately clear what the problem is the last letter of the
variable names were in lower case.
The following files were modified:
modified: 2012/MANIFEST
modified: 2012/hamano/README.md
modified: 2014/MANIFEST
modified: 2015/MANIFEST
modified: 2018/MANIFEST
modified: 2018/anderson/README.md
modified: 2018/ciura/README.md
modified: 2018/ferguson/FILES
modified: 2018/ferguson/weasel.1
modified: 2018/ferguson/weasel.man
modified: 2018/ferguson/weasel.spec
modified: 2019/MANIFEST
modified: 2019/karns/README.md
modified: 2020/MANIFEST
modified: 2020/ferguson2/README.md
modified: 2020/ferguson2/enigma.1
modified: 2020/ferguson2/recode.1
modified: years-spoiler.html
modified: years.html
but I am not clear on some of the changes here. For instance some of the
text changed were html anchors and I'm not sure of the implications of
it other than the fact that changing the filenames (see commits
77fb0f11a2 and
851e191519) would break the links. Whether
more needs to be done or not I do not know.
As per discussions on GitHub the index.html and hint.html files should
be deleted in favour of README.md files (from any
.text/.txt/.markdown/.md files which will be turned into README.md in an
upcoming commit).
The 2020 winners are hinted it, but the source code is not there,
nor are the hints. Someone could look into the HTML and
see what was commented out, but that is not a problem because
WHO won is known and the name of their AWARD is known already.
Moreover a number of the winners have talked about what their
entirs do, so the commented out spoiler text is not a bit problem.
One will find HTML commented out with:
<!-- XXX remove when 2020 is ready
2020 links here
XXX remove when 2020 is ready -->
The "XXX remove when 2020 is ready" string is found at the
start and end comment blocks. Again, soneone could read
what was commented out, but that is OK since most of that
information is known or can be known. The following files
have such HTML comment blocks in them.
./winners.html
./years-spoiler.html
./years.html
In addition, ./all/summary.txt was modified to not
include the 2020 entries for the momemt.
The 2020 winner code AND write-ups are NOT part of this set.
p.s. The all/all.tar.bz2 does not contain the 2020 source code (yet?).
Cody Boone Ferguson