diff --git a/2019/adamovsky/README.md b/2019/adamovsky/README.md index 4dfc0a839..b8b025a7b 100644 --- a/2019/adamovsky/README.md +++ b/2019/adamovsky/README.md @@ -160,7 +160,7 @@ and the call with current continuation `c`. is, how the state of the program is stored and how the Unlambda functions are implemented. -More on this in the **Obfuscation** section. +More on this in the [Obfuscation](#obfuscation) section. ### Build notes: diff --git a/2019/adamovsky/index.html b/2019/adamovsky/index.html index d8bb208bb..c45dabbfd 100644 --- a/2019/adamovsky/index.html +++ b/2019/adamovsky/index.html @@ -505,7 +505,7 @@ and the call with current continuation c. is, how the state of the program is stored and how the Unlambda functions are implemented. -

More on this in the Obfuscation section.

+

More on this in the Obfuscation section.

Build notes:

The program does not require any special treatment by compilers. Some warnings had to be suppressed when compiling with -Wall -Wextra -pedantic. Those were diff --git a/2019/diels-grabsch1/README.md b/2019/diels-grabsch1/README.md index c24c0f22a..7a949f0d2 100644 --- a/2019/diels-grabsch1/README.md +++ b/2019/diels-grabsch1/README.md @@ -55,7 +55,7 @@ compresses differently? The judges know. :) diff -s guidelines.txt guidelines2.txt ``` -Of course you can also use [2015/mills2prog.c](%%REPO_URL%%/2015/mills2/prog.c) instead of +Of course you can also use [2015/mills2](../../2015/mills2/index.html) instead of `zcat` to verify the output file. The achieved compression ratio roughly matches that of the classic Unix `compress(1)` tool. And the source code is very compressed, too: It has exactly the same size as the paragraph you are reading diff --git a/2019/diels-grabsch1/index.html b/2019/diels-grabsch1/index.html index c11ccfaa2..d2ebdfb5c 100644 --- a/2019/diels-grabsch1/index.html +++ b/2019/diels-grabsch1/index.html @@ -432,7 +432,7 @@ compresses differently? The judges know. :)

Check for correctness:

    zcat guidelines.txt.Z > guidelines2.txt
     diff -s guidelines.txt guidelines2.txt
-

Of course you can also use 2015/mills2prog.c instead of +

Of course you can also use 2015/mills2 instead of zcat to verify the output file. The achieved compression ratio roughly matches that of the classic Unix compress(1) tool. And the source code is very compressed, too: It has exactly the same size as the paragraph you are reading diff --git a/2019/dogon/README.md b/2019/dogon/README.md index 7fbd0a166..d382f768d 100644 --- a/2019/dogon/README.md +++ b/2019/dogon/README.md @@ -43,7 +43,7 @@ the program and the script. ...This entry likely concludes the IOCCC category "Cellular automata simulators"; it would be very hard to beat it on its field. -FYI: The `.mc` extension stands for `Golly macrocell` format. +**FYI**: The `.mc` extension stands for `Golly macrocell` format. We truly have not much more to add, except two things: @@ -55,7 +55,9 @@ We truly have not much more to add, except two things: model RAM, you'd want to reduce the value of the Z define in the Makefile to `0x10000000`, otherwise the entry will promptly crash. To do this you can do: - make clobber MEMORY=0x10000000 all +``` + make clobber MEMORY=0x10000000 all +``` Notice that that value must be a power of two! diff --git a/2019/dogon/index.html b/2019/dogon/index.html index fee2aec4d..abc53539d 100644 --- a/2019/dogon/index.html +++ b/2019/dogon/index.html @@ -430,7 +430,7 @@ the program and the script.

2011/blakely, …

…This entry likely concludes the IOCCC category “Cellular automata simulators”; it would be very hard to beat it on its field.

-

FYI: The .mc extension stands for Golly macrocell format.

+

FYI: The .mc extension stands for Golly macrocell format.

We truly have not much more to add, except two things:

+
    make clobber MEMORY=0x10000000 all
+

Notice that that value must be a power of two!

In the interest of saving lives, this entry was not fuzzed.

Author’s remarks:

What is it?

diff --git a/2019/poikola/README.md b/2019/poikola/README.md index 55777378a..00484e116 100644 --- a/2019/poikola/README.md +++ b/2019/poikola/README.md @@ -129,22 +129,16 @@ file `poikola.pdf`. This requires the An old wise man mumbled to me: -``` - Implement a program, which can calculate SHA-3 checksum for a file -- -``` +> Implement a program, which can calculate SHA-3 checksum for a file -- I thought it was easy, but the wizard didn't stop yet: -``` - and primes and Fibonacci numbers. -``` +> and primes and Fibonacci numbers. Still easy. But the [Gandalf the Grey](https://www.glyphweb.com/arda/g/gandalf.html) impersonator was not ready: -``` - But use only `main()`, and do not use `math.h` nor predefined stuff at all. -``` +> But use only `main()`, and do not use `math.h` nor predefined stuff at all. But wait, there are more rules: This work should reflect the extraordinary mind of Matti Nykänen, the all-time best [ski diff --git a/2019/poikola/index.html b/2019/poikola/index.html index 9f0a1d8a1..8f02eca24 100644 --- a/2019/poikola/index.html +++ b/2019/poikola/index.html @@ -472,12 +472,18 @@ file poikola.pdf. This requires the pdfTeX tool.

What this entry does:

An old wise man mumbled to me:

-
    Implement a program, which can calculate SHA-3 checksum for a file --
+
+

Implement a program, which can calculate SHA-3 checksum for a file –

+

I thought it was easy, but the wizard didn’t stop yet:

-
    and primes and Fibonacci numbers.
+
+

and primes and Fibonacci numbers.

+

Still easy. But the Gandalf the Grey impersonator was not ready:

-
    But use only `main()`, and do not use `math.h` nor predefined stuff at all.
+
+

But use only main(), and do not use math.h nor predefined stuff at all.

+

But wait, there are more rules: This work should reflect the extraordinary mind of Matti Nykänen, the all-time best ski jumper and amateur diff --git a/bugs.html b/bugs.html index 27a65ae16..0a074ad5d 100644 --- a/bugs.html +++ b/bugs.html @@ -3186,17 +3186,16 @@ values but his implementation matches that of macOS and FreeBSD.

STATUS: INABIAF - please DO NOT fix

Source code: 2019/ciura/prog.c

Information: 2019/ciura/index.html

-

Cody Boone Ferguson fixed the scripts so -that they can work but it might end up that the scripts don’t show any output -anyway as they use the full alphabet. To test that it works one can have a -script like:

+

The scripts were fixed so that they can work but it might end up that the +scripts don’t show any output anyway as they use the full alphabet. To test that +it works one can have a script like:

    LC_ALL=C  aäbcdefghijklmnoöpqrsßtuüvwxyz | LC_ALL=C grep .. | LC_ALL=de_DE.UTF-8 ./prog aäbcdefghijklmnoöpqrsßtuüvwxyz

If you run this you should see:

    aäbcdefghijklmnoöpqrsßtuüvwxyz

which shows it works. However as the de.sh script refers to all letters it can’t find a perfect pangram. BTW, as far as the question of whether the umlaut -letters or the Eszett are considered letters in the German alphabet, Cody noted -in the de.sh/de.alt.sh scripts:

+letters or the Eszett are considered letters in the German alphabet, it is +noted in the de.sh/de.alt.sh scripts:

    # Are the umlauts ä, ö, ü and Eszett (ß) letters in the German alphabet? There
     # is more than one opinion on the subject but a lot of words do have an umlaut
     # (or Umlaut in German). In some (probably all) systems this script outputs
@@ -3258,29 +3257,22 @@ touched either.

 
Source code: 2019/karns/prog.c

 
Information: 2019/karns/index.html

 
The author stated the following:

-
    - The program must be ran in a terminal that supports ANSI
-      escape codes for moving the cursor and changing colors.
-
-    - Segfaults happen sometimes.
-
-    - I don't know what memory management there is, if any.
-
-    - The program will not compile by an ANSI C compiler: it uses
-      for loops, and it uses C++ style comments. It should compile
-      cleanly using a C99 standard.
-
-    - Breadth first search is slow (and very slow on certain maps),
-      but my A star version of this program is too big.
-
-    - Lots of extra whitespace may be needed if you want to feed in
-      an arbitrary file.
-
-    - It fails to compile on GCC sometimes (according to a friend
-      of mine, I've not encountered this myself).
-
-    - The program could be obfuscated much further.
-
-    - The program contains some unused code and data.

+
 

 
2019/lynn

 

@@ -3302,15 +3294,16 @@ file you should delete all the checkpoint files because the format depends on
 both the network and the input – using the wrong checkpoint is likely to cause
 a crash.

 
The author also wrote:

-
    IMPORTANT NOTE: Since OMLET uses the system stack for network storage,
-    larger networks may cause OMLET to crash (typically with a message like
-    Segmentation fault) unless the system stack size is first increased.
-    The exact command for doing so depends on your shell and your system's
-    hard limits.  On sh/ksh/bash shells, you can view the hard limit
-    with ulimit -Hs and set it with ulimit -s 65532 (replacing 65532
-    with the actual hard limit).  On csh/tcsh shells, you can view
-    the hard limit with limit -h stacksize and set it with
-    limit stacksize 65532 (replacing 65532 with the actual hard limit).

+

+
IMPORTANT NOTE: Since OMLET uses the system stack for network storage, larger
+networks may cause OMLET to crash (typically with a message like Segmentation
+fault) unless the system stack size is first increased. The exact command for
+doing so depends on your shell and your system’s hard limits. On sh/ksh/bash
+shells, you can view the hard limit with ulimit -Hs and set it with ulimit -s
+65532 (replacing 65532 with the actual hard limit). On csh/tcsh shells, you can
+view the hard limit with limit -h stacksize and set it with limit stacksize
+65532 (replacing 65532 with the actual hard limit).

+

 

 
2019/poikola

 

diff --git a/bugs.md b/bugs.md
index 1cfc4e5b5..bfe394c74 100644
--- a/bugs.md
+++ b/bugs.md
@@ -4012,10 +4012,9 @@ values but his implementation matches that of macOS and FreeBSD.
 ### Source code: [2019/ciura/prog.c](%%REPO_URL%%/2019/ciura/prog.c)
 ### Information: [2019/ciura/index.html](2019/ciura/index.html)
 
-[Cody Boone Ferguson](authors.html#Cody_Boone_Ferguson) fixed the scripts so
-that they can work but it might end up that the scripts don't show any output
-anyway as they use the full alphabet. To test that it works one can have a
-script like:
+The scripts were fixed so that they can work but it might end up that the
+scripts don't show any output anyway as they use the full alphabet. To test that
+it works one can have a script like:
 
 ``` 
     LC_ALL=C  aäbcdefghijklmnoöpqrsßtuüvwxyz | LC_ALL=C grep .. | LC_ALL=de_DE.UTF-8 ./prog aäbcdefghijklmnoöpqrsßtuüvwxyz
@@ -4029,10 +4028,10 @@ If you run this you should see:
 
 which shows it works. However as the de.sh script refers to all letters it can't
 find a perfect pangram. BTW, as far as the question of whether the umlaut
-letters or the Eszett are considered letters in the German alphabet, Cody noted
-in the de.sh/de.alt.sh scripts:
+letters or the Eszett are considered letters in the German alphabet, it is
+noted in the de.sh/de.alt.sh scripts:
 
-```
+``` 
     # Are the umlauts ä, ö, ü and Eszett (ß) letters in the German alphabet? There
     # is more than one opinion on the subject but a lot of words do have an umlaut
     # (or Umlaut in German). In some (probably all) systems this script outputs
@@ -4127,31 +4126,20 @@ touched either.
 
 The author stated the following:
 
-```
-    - The program must be ran in a terminal that supports ANSI
-      escape codes for moving the cursor and changing colors.
-
-    - Segfaults happen sometimes.
-
-    - I don't know what memory management there is, if any.
-
-    - The program will not compile by an ANSI C compiler: it uses
-      for loops, and it uses C++ style comments. It should compile
-      cleanly using a C99 standard.
-
-    - Breadth first search is slow (and very slow on certain maps),
-      but my A star version of this program is too big.
-
-    - Lots of extra whitespace may be needed if you want to feed in
-      an arbitrary file.
-
-    - It fails to compile on GCC sometimes (according to a friend
-      of mine, I've not encountered this myself).
-
-    - The program could be obfuscated much further.
-
-    - The program contains some unused code and data.
-```
+- The program must be ran in a terminal that supports ANSI escape codes for
+moving the cursor and changing colors.
+- Segfaults happen sometimes.
+- I don't know what memory management there is, if any.
+- The program will not compile by an ANSI C compiler: it uses for loops, and it
+uses C++ style comments. It should compile cleanly using a C99 standard.
+- Breadth first search is slow (and very slow on certain maps), but my A star
+version of this program is too big.
+- Lots of extra whitespace may be needed if you want to feed in an arbitrary
+file.
+- It fails to compile on GCC sometimes (according to a friend of mine, I've not
+encountered this myself).
+- The program could be obfuscated much further.
+- The program contains some unused code and data.
 
 
 

@@ -4183,17 +4171,14 @@ a crash.
 
 The author also wrote:
 
-```
-    IMPORTANT NOTE: Since OMLET uses the system stack for network storage,
-    larger networks may cause OMLET to crash (typically with a message like
-    Segmentation fault) unless the system stack size is first increased.
-    The exact command for doing so depends on your shell and your system's
-    hard limits.  On sh/ksh/bash shells, you can view the hard limit
-    with ulimit -Hs and set it with ulimit -s 65532 (replacing 65532
-    with the actual hard limit).  On csh/tcsh shells, you can view
-    the hard limit with limit -h stacksize and set it with
-    limit stacksize 65532 (replacing 65532 with the actual hard limit).
-```
+> IMPORTANT NOTE: Since OMLET uses the system stack for network storage, larger
+networks may cause OMLET to crash (typically with a message like Segmentation
+fault) unless the system stack size is first increased.  The exact command for
+doing so depends on your shell and your system's hard limits.  On sh/ksh/bash
+shells, you can view the hard limit with ulimit -Hs and set it with ulimit -s
+65532 (replacing 65532 with the actual hard limit).  On csh/tcsh shells, you can
+view the hard limit with limit -h stacksize and set it with limit stacksize
+65532 (replacing 65532 with the actual hard limit).
 
 

 ## 2019/poikola