'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
@@ -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 its own domain. The IOCCC has an official home page is now:
|
||||
|
||||
|
||||
@@ -16,7 +16,7 @@
|
||||
|
||||
cat horizon.sc pittsburgh.sc | ./banks
|
||||
|
||||
## Judges' comments:
|
||||
## Judges' remarks:
|
||||
|
||||
What can we say? It's a flight sim done in 1536 bytes of real code.
|
||||
This one is a real marvel. When people say the size limits are too
|
||||
@@ -24,9 +24,9 @@ tight, well, we can just point them at this one. This program really
|
||||
pushes the envelope!
|
||||
|
||||
The provided Makefile should work; you will need an X-ish system, and
|
||||
a select() system call. More on building in the author comments.
|
||||
a select() system call. More on building in the author remarks.
|
||||
|
||||
## Author's comments:
|
||||
## Author's remarks:
|
||||
|
||||
You have just stepped out of the real world and into the
|
||||
virtual. You are now sitting in the cockpit of a Piper Cherokee
|
||||
|
||||
+2
-2
@@ -23,7 +23,7 @@ or:
|
||||
|
||||
./bas1 | gunzip | gs -sDEVICE=pgmraw -sOutputFile='|xv -' -
|
||||
|
||||
## Judges' comments
|
||||
## Judges' remarks
|
||||
|
||||
The output is supposed to be a 3D maze, but it is somewhat more
|
||||
than that. If you've seen any of the Maurits Escher's works,
|
||||
@@ -31,7 +31,7 @@ you'll know what we're talking about.
|
||||
|
||||
When trying to run the program with command line arguments, be generous.
|
||||
|
||||
## Author's comments
|
||||
## Author's remarks
|
||||
|
||||
BEMAZING
|
||||
========
|
||||
|
||||
+2
-2
@@ -14,7 +14,7 @@
|
||||
|
||||
./bas2 < bas2.c
|
||||
|
||||
## Judges' comments:
|
||||
## Judges' remarks:
|
||||
|
||||
### Questions to ponder:
|
||||
|
||||
@@ -32,7 +32,7 @@ a way that differs from a strict reading of one of the
|
||||
official IOCCC rules. What is the rule and what is the octet
|
||||
value?
|
||||
|
||||
## Author's comments:
|
||||
## Author's remarks:
|
||||
|
||||
The main obfuscation is the way characters are recognized, which is
|
||||
done by matching the bit patterns. Minor obfuscations are:
|
||||
|
||||
+3
-3
@@ -14,7 +14,7 @@
|
||||
|
||||
./df
|
||||
|
||||
## Judges' comments;
|
||||
## Judges' remarks;
|
||||
|
||||
Everyone talks about how data hiding can produce clearer code; I am
|
||||
pleased to offer this charming refutation.
|
||||
@@ -37,7 +37,7 @@ Extra credit questions:
|
||||
- How many words does this entry use?
|
||||
- Can you add more words to the program and still make it work?
|
||||
|
||||
## Author's comments
|
||||
## Author's remarks
|
||||
|
||||
This program lets you guess English words. It displays an underscore
|
||||
for each letter in the word; guessing a letter that actually is in
|
||||
@@ -107,7 +107,7 @@ reverse them. Anyone out there should have enough discipline and
|
||||
rot13 shouldn't be required, really. After all, we are no children
|
||||
anymore :-)
|
||||
|
||||
This paragraph is not part of the author's comments, but is a helpful
|
||||
This paragraph is not part of the author's remarks, but is a helpful
|
||||
gift from the judges; if you read too fast to stop yourself, this should
|
||||
give you enough time to stop, which you really need to do RIGHT NOW if
|
||||
you don't want to read the spoilers, which really do spoil everything,
|
||||
|
||||
@@ -16,7 +16,7 @@
|
||||
|
||||
./dlowe < anyfile > pootfile
|
||||
|
||||
## Judges' comments
|
||||
## Judges' remarks
|
||||
|
||||
Why is this entry would be considered a utility? Well because it
|
||||
is able to convert content-free web pages into useful web pages.
|
||||
@@ -66,7 +66,7 @@ that version try:
|
||||
make dlowe.alt
|
||||
./dlowe.alt < anyfile > pootfile
|
||||
|
||||
## Author's comments
|
||||
## Author's remarks
|
||||
|
||||
This program is a text filter, it reads stdin and outputs the
|
||||
"corrected" text to stdout.
|
||||
|
||||
@@ -16,16 +16,16 @@
|
||||
|
||||
./pootris
|
||||
|
||||
## Judges' comments
|
||||
## Judges' remarks
|
||||
|
||||
Read the Author's comments below. We believe that your experience may
|
||||
Read the Author's remarks below. We believe that your experience may
|
||||
mirror one of our experiences:
|
||||
|
||||
> Originally, I didn't appreciate the game. Then I actually read the
|
||||
> description of the controls. I started playing. I struggled.
|
||||
> I spelled my first "poot". I was hooked ...
|
||||
|
||||
## Author's comments
|
||||
## Author's remarks
|
||||
|
||||
Usage:
|
||||
|
||||
|
||||
@@ -25,7 +25,7 @@
|
||||
echo 'HOW DOES IT DO THAT' | ./dorssel
|
||||
echo 'HOW DOES IT DO THAT' | ./dorssel | ./dorssel
|
||||
|
||||
## Judges' comments:
|
||||
## Judges' remarks:
|
||||
|
||||
How does the program decide which way to convert?
|
||||
|
||||
@@ -50,7 +50,7 @@ Extra credit: Change the program so that it does not SHOUT IN ALL CAPS.
|
||||
|
||||
You might also want to read the [dorssel.hint](dorssel.hint) file.
|
||||
|
||||
## Author's comments:
|
||||
## Author's remarks:
|
||||
|
||||
Usage
|
||||
=====
|
||||
|
||||
+2
-2
@@ -46,7 +46,7 @@ sample expressions that you can use:
|
||||
)
|
||||
)
|
||||
|
||||
## Judges' comments:
|
||||
## Judges' remarks:
|
||||
|
||||
This program translates lambda expressions into combinator
|
||||
expressions. But you do not need to know Lambda Calculus to be
|
||||
@@ -76,7 +76,7 @@ combinator expressions on standard output.
|
||||
What do you have to do to make this program work with an old non-ANSI C
|
||||
preprocessor?
|
||||
|
||||
## Author's comments:
|
||||
## Author's remarks:
|
||||
|
||||
My program is a demonstration of some practical applications of
|
||||
theoretical computer science. The application it implements is a program
|
||||
|
||||
@@ -72,7 +72,7 @@ To use this version use `schweikh1.alt` instead.
|
||||
|
||||
./schweikh1
|
||||
|
||||
## Judges' comments:
|
||||
## Judges' remarks:
|
||||
|
||||
What does it do? It seems to print a list of system headers, perhaps
|
||||
with words after them. Curiously, if you look at the list of words
|
||||
@@ -85,7 +85,7 @@ whether or not it should. The innovative realization that you can
|
||||
use special characters, such as '\n', in #file directives alone
|
||||
merits some recognition.
|
||||
|
||||
I've included most of the author's comments; they're fairly thorough.
|
||||
I've included most of the author's remarks; they're fairly thorough.
|
||||
Do not read them if you want to figure this out yourself. "Amendment
|
||||
One" refers to "NA1", the add-on to C89 which added some fairly
|
||||
crufty internationalization support.
|
||||
@@ -97,7 +97,7 @@ gcc invocation anyway. Anyone who uses egcs and has no plain gcc
|
||||
will need to frob the source anyway and can be expected to do the
|
||||
right thing with ${CC}. So use gcc.
|
||||
|
||||
## Author's comments
|
||||
## Author's remarks
|
||||
|
||||
Important! This program, if it compiles at all, is mis-compiled by many
|
||||
compilers due to compiler bugs. It could be the "least likely
|
||||
|
||||
@@ -44,7 +44,7 @@ What happens if you don't put in any number like the below?
|
||||
<ENTER>
|
||||
|
||||
|
||||
## Judges' comments:
|
||||
## Judges' remarks:
|
||||
|
||||
Run the program with a small argument, like 5 or 10, several times. Are the
|
||||
results different? Why?
|
||||
@@ -103,7 +103,7 @@ email the author for a free pat on the back.
|
||||
NOTE: the author submitted the program as yarng so when trying the examples
|
||||
below change `yarng` to `./schweikh2`.
|
||||
|
||||
## Author's comments:
|
||||
## Author's remarks:
|
||||
|
||||
What this program does
|
||||
----------------------
|
||||
|
||||
@@ -29,7 +29,7 @@ If you're in this winning entry's directory:
|
||||
Notice that the tool finds a duplicate file, that of the man page.
|
||||
|
||||
|
||||
## Judges' comments:
|
||||
## Judges' remarks:
|
||||
|
||||
Maybe you will not need to buy another 10 Gb disk to store them. :-)
|
||||
|
||||
@@ -48,7 +48,7 @@ Notice that the tool finds a duplicate file, that of the man page.
|
||||
NOTE: Some non-gcc compilers that are not fully ANSI standard do
|
||||
not compile this entry correctly.
|
||||
|
||||
## Author's comments
|
||||
## Author's remarks
|
||||
|
||||
The source is expected to conform to IEEE Std 1003.1-1990 ("POSIX").
|
||||
Thank God the IEEE does not standardize a coding style...
|
||||
|
||||
@@ -16,7 +16,7 @@
|
||||
|
||||
./tomtorfs tomtorfs.c 32 04C11DB7 1 FFFFFFFF FFFFFFFF
|
||||
|
||||
## Judges' comments
|
||||
## Judges' remarks
|
||||
|
||||
Also try:
|
||||
|
||||
@@ -31,7 +31,7 @@
|
||||
of the program with the value of CRC computed by PKZIP or any other
|
||||
archiver that uses the CRC-32 algorithm.
|
||||
|
||||
## Author's comments
|
||||
## Author's remarks
|
||||
|
||||
Usage:
|
||||
crc filename bitwidth polynom reflected init xor
|
||||
|
||||
Reference in new issue
Block a user