'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'
2023-04-10 11:01:39 -07:00
1 parent 508b760db4
commit 4bf3f302cb
@@ -7,7 +7,7 @@ Standard IOCCC stuff
 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 IOCCC has an official home page:

@@ -30,7 +30,7 @@
 	cat parse.oo fac.oc | ./august | ./august


-## Judges' comments:
+## Judges' remarks:

 This entry can feed on itself.  If you C preprocess the source,
 you compile the interpreter:
@@ -59,7 +59,7 @@ We (the judges) recommend that you spend some time studying this
 entry as it surely will make the 'best of the IOCCC' list.  It was
 very well received by those who attended the IOCCC BOF.

-## Author's comments
+## Author's remarks

 This program is a bytecode interpreter.  This fact is not
 particularly obfuscated; any experienced C programmer can see that
@@ -37,7 +37,7 @@ thanks to Yusuke for confirming the output is correct!
 Why does the output end with 121?


-## Judges' comments:
+## Judges' remarks:

 The output is mis-leading ... why does it also print 2047?

@@ -51,7 +51,7 @@ We (the judges) recommend that you take the time needed to understand
 how this program works.  The source is small enough to make the effort
 reasonable, and complex enough to make it interesting.

-## Author's comments:
+## Author's remarks:

 This program assumes that your terminal wraps lines automatically.
 If this is not the case, you may need to change the space in the
@@ -18,12 +18,12 @@ WARNING: on modern systems this is very fast and could be a problem for those
 susceptible to photosensitivity. Please try this one with caution if this
 applies to you! The same goes for people who can be overstimulated.

-## Judges' comments
+## Judges' remarks

 We were impressed by the author's ability to render spheres in 3D 
 in a very small chunk of code.

-## Author's comments
+## Author's remarks

 This program shows flying spheres. The program eats CPU on lesser
 equipped systems. The program will run until termination. Terminal 
@@ -39,14 +39,14 @@ Care to guess why these execute differently?  Only the
 compiler knows ... ok maybe other things like the author,
 the judges and maybe you too?

-## Judges' comments
+## Judges' remarks

 For mis-leading C pre-processor output, try:


 	cc -E gandalf.c

-## Author's comments
+## Author's remarks

 The program requires an ASCII system.

@@ -26,7 +26,7 @@ and/or running on modern systems.
 	echo 'CC OR NOT CC' | ./huffman | ./huffman


-## Judges' comments:
+## Judges' remarks:

 If you are still confused and want to read a spoiler, check out
 the source and it will be clear as mud!
@@ -39,7 +39,7 @@ And if you really can't see what is going on, here is an extra spoiler:

 This entry was very well received at the IOCCC BOF.

-## Author's comments:
+## Author's remarks:

 This filter program is really not obfuscated code.  It compiles cleanly
 with an ANSI C compiler and comes with user documentation that even a
@@ -20,13 +20,13 @@

 	./jonth host1:0 host2:0

-## Judges' comments:
+## Judges' remarks:


 For extra credit, figure out how you can cheat by taking over
 a square already occupied by an opponent.

-## Author's comments:
+## Author's remarks:

 This is multi-user tic-tac-toe for X Windows. You may give one or two X
 displays as arguments to this game.
@@ -20,13 +20,13 @@ For more information try:
 	./rcm < rfc1952.gz


-## Judges' comments:
+## Judges' remarks:

 For a good noop try:

 	gzip -c < rcm.c | ./rcm

-## Author's comments:
+## Author's remarks:

 Except for some silly requirements regarding input validation, CRC
 checking, and similar unimportant fluff, this program is a fully
@@ -16,7 +16,7 @@

 	./schweikh1

-## Judges' comments:
+## Judges' remarks:

 Look at the source.  There is something very odd going on here.  
 Where does the real code come from if everything is a C pre-processor 
@@ -25,7 +25,7 @@ statement?
 Clearly this is either the Best Use or the Worst Abuse of the
 C Preprocessor that the judges have seen this year!

-## Author's comments:
+## Author's remarks:

 What this program does
 ----------------------
@@ -35,7 +35,7 @@ What happens if you pass only three parameters like the below?

        ./schweikh2 15 1 0

-## Judges' comments:
+## Judges' remarks:


 The original program, with only slight obfuscations, may be found
@@ -45,7 +45,7 @@ in `hunni.c`.  The perl script, obfuscates it appropriately:

 This entry was another crowd pleaser at the IOCCC BOF.

-## Author's comments:
+## Author's remarks:

 Note: the source must be viewed with tabstop 8. To appreciate the
 beauty have your eyes half closed.
@@ -22,7 +22,7 @@ You have been warned.
 	./schweikh3


-## Judges' comments:
+## Judges' remarks:

 The source fails to compile on compilers that recognize the inline
 keyword by default.  For gcc, you may need to use -ansi.
@@ -41,7 +41,7 @@ NOTE: On some systems such as SunOS, one may need to compile with:
 	      -I. -D_POSIX_SOURCE '-Ddifftime(a,b)=(double)(b-a)' \
 	      schweikh3.c -o schweikh3

-## Author's comments:
+## Author's remarks:

 Why I think my entry is obfuscated
 ----------------------------------
@@ -55,14 +55,14 @@ To compile this alternate version:
 make alt
 ```

-## Judges' comments:
+## Judges' remarks:

 Time and time again, Brian Westley seems to come up with a winner!
 We are amazed at how much is being done with only one relatively
 short line.  We think you will as well if you take the time to
 understand it.

-## Author's comments:
+## Author's remarks:

 This 1-line program allows various analog ASCII clocks
 to print out the time; the ASCII clock is built from