'comments' -> 'remarks' in all README.md files
As in
sgit -e 's/\([Aa]uthor.*\)comments/\1remarks/g' -e 's/\([Jj]udge.*\)comments/\1remarks/g' '*README.md'
This commit is contained in:
1 parent
508b760db4
commit
4bf3f302cb
341 files changed
+655
-655
No files matched your search
+1
-1
@@ -4,7 +4,7 @@
|
||||
Look at the README.md file for the given winner for information
|
||||
on how to compile the winner and how to run the winning program.
|
||||
Look at the winning source and try to figure how it does what it does!
|
||||
You may then wish to look at the Author's comments for even more details.
|
||||
You may then wish to look at the Author's remarks for even more details.
|
||||
|
||||
The maximum size of entries was raised from 1024 to 1536 bytes, however
|
||||
smaller entries were encouraged. Due to the ["Best Abuse of the Rules"
|
||||
|
||||
@@ -16,7 +16,7 @@
|
||||
|
||||
./applin
|
||||
|
||||
## Judges' comments:
|
||||
## Judges' remarks:
|
||||
|
||||
This entry is by far the most unusual abuse of the C preprocessor that
|
||||
we have received thus far. Nearly all of the real work is done in the
|
||||
|
||||
+1
-1
@@ -63,7 +63,7 @@ Thank you Cody for your assistance!
|
||||
NOTE: in linux it might happen that core dumps are created when running this
|
||||
entry even though it works fine.
|
||||
|
||||
## Judges' comments
|
||||
## Judges' remarks
|
||||
|
||||
This entry has a very twisted flow of control via recursion, iteration
|
||||
and multi-processing. Try to understand what is being done with the
|
||||
|
||||
@@ -35,7 +35,7 @@ using that macro for `#define`. This version will not likely work on modern
|
||||
systems if you can even get it to compile.
|
||||
|
||||
|
||||
## Judges' comments:
|
||||
## Judges' remarks:
|
||||
|
||||
NOTE: The program relies heavily on ASCII. Don't even think of running it on
|
||||
an EBCDIC machine. If you name the file anything other than "isaak.c", you must
|
||||
|
||||
@@ -12,7 +12,7 @@
|
||||
./litmaath eschew obfuscation
|
||||
|
||||
|
||||
## Judges' comments:
|
||||
## Judges' remarks:
|
||||
|
||||
Note the unusual structure:
|
||||
|
||||
|
||||
@@ -23,7 +23,7 @@ be `char **` :-) ) with the correct args it now works. Thank you Cody for your
|
||||
assistance!
|
||||
|
||||
|
||||
## Judges' comments
|
||||
## Judges' remarks
|
||||
|
||||
Compile and run without parameters.
|
||||
|
||||
|
||||
@@ -18,7 +18,7 @@
|
||||
char *(*(fun[16])();
|
||||
|
||||
|
||||
## Judges' comments
|
||||
## Judges' remarks
|
||||
|
||||
This is a somewhat restricted version of a useful program that has been
|
||||
posted to Usenet. What is unusual is what it is able to do so much
|
||||
|
||||
@@ -55,7 +55,7 @@ For clang try the alt code like:
|
||||
|
||||
NOTE: you need to make clobber first for this entry to work right.
|
||||
|
||||
## Judges' comments:
|
||||
## Judges' remarks:
|
||||
|
||||
We enjoyed this entry this year, however in the future programs must be able to
|
||||
be compiled from within a Makefile without the need of human intervention.
|
||||
@@ -64,7 +64,7 @@ Meanwhile Cody was twisted enough to point out (though to be fair he felt sick
|
||||
doing this) that with a slight modification this entry can be C++ instead. We don't
|
||||
thank him for this ghastly point! :-)
|
||||
|
||||
## Author's comments:
|
||||
## Author's remarks:
|
||||
|
||||
This program can be configured to do almost everything. The configuration is
|
||||
done during compile time by typing in, C code, that one would like the program
|
||||
|
||||
@@ -15,7 +15,7 @@
|
||||
./westley
|
||||
|
||||
|
||||
## Judges' comments
|
||||
## Judges' remarks
|
||||
|
||||
Your compiler must parse
|
||||
|
||||
|
||||
Reference in new issue
Block a user