Files
ioccc/1994/ldb
Landon Curt Noll e9c3ec7ce7 fix bin/tar-entry.sh
Fixed when the `.tar.tstamp` file is updated
by `bin/tar-entry.sh`.

Changed `bin/tar-entry.sh` VERSION from "1.3 2024-03-22"
to "1.3.1 2024-03-25".

Performed `make form_entry_tarball` to complete the test of the above.

TODO: Test the results under Linux.

TODO: Update `bin/tar-year.sh`.  Update year level compressed tarballs.

TODO: Update `bin/tar-all.sh`.  Update top level compressed tarball.

TODO: Write `bin/untar-year.sh` and `bin/untar-all.sh`.
2024-03-25 23:24:09 -07:00
..
2024-03-22 23:34:37 -07:00
2024-03-25 23:24:09 -07:00
2024-03-25 23:24:09 -07:00
2024-03-25 22:44:34 -07:00
2023-07-07 10:38:29 -07:00
2023-07-06 21:49:38 -07:00
2024-03-20 00:19:52 -07:00
2024-03-11 09:09:21 -07:00

To build:

make all

Bugs and (Mis)features:

The current status of this entry is:

STATUS: INABIAF - please **DO NOT** fix

For more detailed information see 1994 ldb bugs.

To use:

./ldb < file

some_command | ./ldb

Try:

./try.sh

Judges' remarks:

Trigraphs are natural obfuscators. Most C-beautifiers become C-uglifiers because they don't handle them correctly.

Can you figure out how it prints a given random line (or if the line is longer than 231 characters, part of that line) from stdin?

Author's remarks:

All input lines must be under 232 characters long. The compiling platform should be ASCII based.