Landon Curt Noll
f07fec3a98
Eliminated the need for the `.tar.tstamp` files. It became intractable
to produce a tarball that was byte-for-byte identical to a tarball
on another platform. We further simplified the process used by the
`bin/tar-year.sh` tool to no longer need `.tar.tstamp` files.
Removed `.tar.tstamp` files and updated the manifest.
Sorry (tm Canada 🇨🇦) for the "flip-flop".
The `bin/tar-year.sh` tool now uses a similar algorithm to how
`bin/tar-entry.sh` determines if a compressed tarball needs to be
rebuilt.
Changed `bin/tar-entry.sh` VERSION from "1.3.3 2024-03-27"
to "1.3.4 2024-03-27".
Changed `bin/tar-year.sh` VERSION from "1.1.3 2024-03-27"
to "1.2 2024-03-27".
Performed `make www` and `make form_entry_tarball`
and `make form_year_tarball` to complete the above
actions and test these changes under macOS.
TODO: Test the `bin/tar-year.sh` tool under Linux.
TODO: Address issues with building the top level `ioccc.tar.bz2`
and the `bin/tar-all.sh` tool and the `make form_all_tarball` rule.
NOTE: The `bin/tar-all.sh` tool and the `make form_all_tarball` rule
and the `make tar` should **NOT** be used at this time.
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.
Spoiler: Open the source with an editor like vim or emacs.