Landon Curt Noll
d981aa2a04
The PR #2662 introduced TAB characters into entry `.entry.json` files and mal-formatted `author_handle` JSON members. To restore canonical JSON formatting, we did: ```sh find [12][90][89012][0-9] -name .entry.json -print | xargs -n 1 bin/jfmt-wrapper.sh -v 1 ``` BTW: We have written a tool, currently untested, to do this. We plan to also add a new fix JSON format rule to the top level `Makefile`. Performed `make www` to accomplish the above and to test under macOS.
To build:
make
To use:
./prog
Try:
./try.sh
Judges' remarks:
At this point you might be wondering, WTF?*
-
What The Freak (polite form)
-
What's This For? (you may be wondering)
-
What the Fish (python form)
How is this code obfuscated? Well look again:
less prog.c
more prog.c
Where did those underscores come from? Well RTFS!**
** Read the Freaking Source (polite form) ** Read The Freaking Screen (polite form)
If you are still puzzled, look at prog.c with your favorite text editor.
Author's remarks:
Follow these instructions literally!
cat prog.c
gcc -w -o prog prog.c
./prog
You will do a double take.
Hint 1: Do less prog.c. You will see an emphasized string if your
terminal supports bold.
Hint 2: Do wc -c prog.c. This is very long one-liner.
Hint 3: Open the source with an editor like vim or emacs.