'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
@@ -28,7 +28,7 @@ make

 ./prog http://127.0.0.1:1701

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

 Port 1701?  Well this is not the l2f registered TCP/1701 protocol.
 Sniff the traffic to/from that port.  You will see HTTP client
@@ -41,7 +41,7 @@ binary content communicated between client and server.
 So how does this program do it?  A trek though the cloak of
 obfuscation awaits the reader of the source!

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

 ### Abstract

@@ -24,14 +24,14 @@ make
 Changing bounding box coordinates in the source to explore
 various regions of the fractal.

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

 We consider this entry a tribute to all "Abuse of the C preprocessor"
 and Mandelbrot fractal drawing entries we've seen over the years.

 We liked the use of unary notation facilitated by variadic macros.

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

 ### Portability

@@ -25,7 +25,7 @@ make main
 ./main Hello
 ```

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

 Big terminals with tiny fonts have their uses in certain cases.
 One of them is:
@@ -40,7 +40,7 @@ When using a smart phone to read the output, you may need to
 step back to see the bigger picture because that picture is worth
 more than 1000 words.

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

 ### Remarks

@@ -26,13 +26,13 @@ make hello
 ./hello
 ```

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

 If you look closely at the source, you will see code that appears
 to puts C code that includes itself.  How and why?  Perhaps it is
 in the DNA code of the code? Perhaps there are 23 reasons? :-)

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

 ### Remarks

@@ -81,12 +81,12 @@ cat giana.level | ./prog 320 200 1000 300 192 168 giana.rgba giana8.wav 5459393
 cat mario.level | ./prog 320 200 800 300 128 144 mario.rgba mario8.wav 10343679 && telnet towel.blinkenlights.nl
 ```

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

 A classic for a particular generation. Like all good programs, being data
 driven means you can do fun things in small spaces.

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

 ### Remarks

@@ -22,7 +22,7 @@ make
 cat image.rgb | ./prog '  .,:;!$#@'
 ```

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

 On the face of it :-) given what this program one might wonder what makes this winner special.
 But when you realize the source is small enough to tweet on twitter you understand.
@@ -30,7 +30,7 @@ But when you realize the source is small enough to tweet on twitter you understa
 Who will be the first to tweet this source?  How many re-tweets will such tweet get?
 And how many people will really understand the tweet?

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

 ### Remarks

@@ -34,14 +34,14 @@ make
 ls
 ```

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

 Think of this as a Maker Faire's make.  :-)

 It works reasomably well.  While not super ultra-featured, it does fair well with the Makefile we supplied.
 Not only that, it helped uncover a bug we had in our special Makefile rules.

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

 ### Remarks

@@ -22,13 +22,13 @@ cp -f sinon.c run.c; ./hecate.sh
 cp -f sinon.c run.c; ./hecate.sh; ./glock.sh; sleep 3; ./glock.sh; sleep 1; ./hecate.sh
 ```

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

 Try to figure out how this entry determines the optimization level with
 which it had been compiled. Is this an example of undefined behavior
 or unspecified behavior?

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

 ### Summary

@@ -26,7 +26,7 @@ HINT: Try pressing the left and right arrow keys as needed.
 Also try pressing space/enter to select options.
 Pressing Q or Escape may end the fun before you are ready. :-)

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

 When the code looks like lemons, it is probably because the LEMONPEOPLE,
 or at least the LEMONLORD was involved. :-)
@@ -40,7 +40,7 @@ is being written to a file and then compiled.  And yet that compiled
 code is somehow executed from main.  But how?  How is main able to
 call code that was written and compiled just in time for execution?

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

 ### TABLE OF CONTENTS

@@ -24,7 +24,7 @@ echo 'Want to hear me beep?' | ./prog > audio_file.raw
 echo 'No. I want chocolate!' | ./prog | mplayer -demuxer rawaudio -
 ```

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

 This program sets a new tone for obfuscation. But do you understand
 what it says about obfuscation? Perhaps:
@@ -46,7 +46,7 @@ NOTE: In 2020 [Cody Boone Ferguson](/winners.html#Cody_Boone_Ferguson) found a
 minor bug when working on his [Enigma machine entry](../../2020/ferguson2); see
 his [README.md](../../2020/ferguson2/README.md) for details (search for `vik`).

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

 ### Remarks

@@ -21,7 +21,7 @@ make
 cc -E prog.c | indent | sed '1,/5.*prog/d'
 ```

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

 C11 features definitely help this entry to be as concise as it is.

@@ -29,7 +29,7 @@ The judges would like to think that they had almost understood how this entry wo

 If you win a bet by demonstrating this entry, please let us know.

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

 ### Remarks