cleanup winner README.md files
Fixed cases where there was a bad trailing backslash. Improved a few cases where a code block was needed to highlight some text. Changed a few cases where a code block needed to declared as, say, a sh code block. Fixed a few cases where the winner information was not properly formatted. Plus a few nits and clarifying text was added.
This commit is contained in:
1 parent
394f710bc3
commit
360708f858
120 files changed
+1198
-1024
No files matched your search
@@ -2,7 +2,7 @@
|
||||
|
||||
David Lowe\
|
||||
US\
|
||||
<j.david.lowe@gmail.com>
|
||||
<j.david.lowe@gmail.com>\
|
||||
<https://github.com/dlowe>
|
||||
|
||||
|
||||
|
||||
@@ -47,9 +47,11 @@ Pressing `d` drops the current letter onto the board.
|
||||
Read the authors' remarks below to find out how to play. 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 ...
|
||||
```
|
||||
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 remarks:
|
||||
@@ -69,7 +71,7 @@ around the border of the playing board, and decide when and where to drop
|
||||
it into the board. Sound easy? Of course, there's a catch...
|
||||
|
||||
### Controls
|
||||
\
|
||||
|
||||
Only three controls:
|
||||
|
||||
'a' moves the current letter one position counterclockwise around
|
||||
@@ -160,7 +162,6 @@ places.
|
||||
|
||||
- Some way of quitting gracefully.
|
||||
|
||||
|
||||
Good Luck!
|
||||
|
||||
|
||||
|
||||
+10
-10
@@ -1,7 +1,7 @@
|
||||
# Most Obfuscated Translator
|
||||
|
||||
Tony Finch
|
||||
United Kingdom
|
||||
Tony Finch\
|
||||
United Kingdom\
|
||||
<https://dotat.at>
|
||||
|
||||
|
||||
@@ -179,24 +179,24 @@ couple of simple optimisations. For example, note that `K (a b)` is the
|
||||
same as `S (K a) (K b)`, because
|
||||
|
||||
```
|
||||
K (a b) x
|
||||
-> a b
|
||||
K (a b) x
|
||||
-> a b
|
||||
```
|
||||
|
||||
and
|
||||
|
||||
```
|
||||
S (K a) (K b) x
|
||||
-> K a x (K b x)
|
||||
-> a b
|
||||
S (K a) (K b) x
|
||||
-> K a x (K b x)
|
||||
-> a b
|
||||
```
|
||||
|
||||
Also, `S (K a) I` is the same as just `a` because
|
||||
|
||||
```
|
||||
S (K a) I x
|
||||
-> K a x (I x)
|
||||
-> a x
|
||||
S (K a) I x
|
||||
-> K a x (I x)
|
||||
-> a x
|
||||
```
|
||||
|
||||
The program simply reads a lambda expression from the standard input,
|
||||
|
||||
@@ -1,7 +1,7 @@
|
||||
# Best Flow Control
|
||||
|
||||
Mark Schnitzius
|
||||
US
|
||||
Mark Schnitzius\
|
||||
US\
|
||||
<http://computronium.org/ioccc.html>
|
||||
|
||||
|
||||
|
||||
+20
-20
@@ -221,19 +221,19 @@ C compilers.
|
||||
must resemble one of the canonical forms, `"foo.h"` or `<bar.h>`.
|
||||
This lets us write things like
|
||||
|
||||
```c\
|
||||
#define HEADER "foo.h"
|
||||
#include HEADER
|
||||
```
|
||||
```c
|
||||
#define HEADER "foo.h"
|
||||
#include HEADER
|
||||
```
|
||||
|
||||
I could not find a compiler rejecting this. However, if we're
|
||||
torturing the preprocessor a little more, by using token pasting,
|
||||
at least one compiler falls over.
|
||||
|
||||
```c
|
||||
#define H(x) <st##x##.h>
|
||||
#include H(dio) /* expands to <stdio.h> */
|
||||
```
|
||||
```c
|
||||
#define H(x) <st##x##.h>
|
||||
#include H(dio) /* expands to <stdio.h> */
|
||||
```
|
||||
|
||||
is rejected by tcc version 4.1.2, the TenDRA compiler:
|
||||
```
|
||||
@@ -253,21 +253,21 @@ C compilers.
|
||||
ISO 6.8.4. ISO 6.1.4 defines string literals as s-char-sequences,
|
||||
which may include octal escape sequences. Let's look at
|
||||
|
||||
```c
|
||||
#include <stdio.h>
|
||||
#line 42 "foo\0bar"
|
||||
int main (void) {
|
||||
printf ("%s %d\n", __FILE__, (int)sizeof __FILE__);
|
||||
return 0;
|
||||
}
|
||||
```
|
||||
```c
|
||||
#include <stdio.h>
|
||||
#line 42 "foo\0bar"
|
||||
int main (void) {
|
||||
printf ("%s %d\n", __FILE__, (int)sizeof __FILE__);
|
||||
return 0;
|
||||
}
|
||||
```
|
||||
|
||||
This is supposed to output `'foo 8'`. Here's what happens in RL:
|
||||
|
||||
```
|
||||
foo 4 gcc 2.7.2.1, lcc
|
||||
foo\0bar 9 tcc 4.1.2, Sunsoft cc turn "\0" into "\\0", ugh!
|
||||
```
|
||||
```
|
||||
foo 4 gcc 2.7.2.1, lcc
|
||||
foo\0bar 9 tcc 4.1.2, Sunsoft cc turn "\0" into "\\0", ugh!
|
||||
```
|
||||
|
||||
(I have written a bug report for gcc. Newer versions and egcs are ok.)
|
||||
|
||||
|
||||
@@ -54,7 +54,7 @@ make schweikh2
|
||||
|
||||
often produced an error of the form:
|
||||
|
||||
```
|
||||
```sh
|
||||
gcc -ansi schweikh2.alt.c -o schweikh2.alt
|
||||
as: Error: cca00NzV.s, line 58: Missing " at end of string
|
||||
"
|
||||
|
||||
Reference in new issue
Block a user