mirror/ioccc
1
0 Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

replace trailing whitespace with blackslash in README.md

Browse Source 
As an alternative to the markdown trailing whitespace as a line
break, we use a trailing blackslash as a markdown line break.
This commit is contained in:
Landon Curt Noll committed 2023-10-18 15:49:51 -07:00
1 parent ddb78f6f33
commit 6625034139
263 files changed
+1181 -1181
Download Patch File Download Diff File Expand all files Collapse all files

No files matched your search

2018/algmyr/README.md
+1 -1
View File
@@ -31,7 +31,7 @@ echo '<<<<<< /\_/\_/\ _-_-_-_ !!!!! :.:.:.: >>>>>> ****** ~~~~~~~' |
./prog | aplay -c1 -fFLOAT_LE -r44100
# Assuming sox:
echo -n ' MENE MENE TEKEL UPHARSIN ' | ./prog |
echo -n ' MENE MENE TEKEL UPHARSIN ' | ./prog |\
sox -t raw -c 1 -r 44100 -L -e floating-point -b 32 - -n spectrogram -d 10 -X 300
# now open spectrogram.png with a graphics viewer or editor
2018/bellard/README.md
+2 -2
View File
@@ -1,6 +1,6 @@
# Most inflationary
Fabrice Bellard
Fabrice Bellard\
<https://bellard.org/>
## To build:
@@ -68,7 +68,7 @@ as the algorithms already have a significant complexity.
Although the program was optimized to decompress its built-in image,
it accepts to decompress image files from its standard
input. Examples:
\
```sh
./prog d < lena512.bin > lena512.ppm
./prog d < fruits.bin > fruits.ppm
2018/burton1/README.md
+2 -2
View File
@@ -1,6 +1,6 @@
# Best one-liner
Dave Burton
Dave Burton\
<http://ioccc.snox.net>
## To build:
@@ -209,7 +209,7 @@ page 71, remarks:
> that accepts a variable number of arguments, because there is no portable way
> for the called function to determine how many arguments where actually passed
> to it in a given call.
> ...
> ...\
> `printf`, the most common C function with a variable number of arguments,
> ... is also non-portable and must be modified for different environments.
2018/burton2/README.md
+28 -28
View File
@@ -1,6 +1,6 @@
# Best abuse of the rules
Dave Burton
Dave Burton\
<http://ioccc.snox.net>
## To build:
@@ -45,45 +45,45 @@ that is saying something! What is this program weighing and how much does it we
### tac - tokenize and count C and derivative languages:
```
tac computes C program size
(obfuscated / otherwise)
by splitting code as tokens small,
tac computes C program size\
(obfuscated / otherwise)\
by splitting code as tokens small,\
ignoring space, then counting all.
It tries quite hard to act the same
as counting tool of I-OCCC fame.
It tries quite hard to act the same\
as counting tool of I-OCCC fame.\
Some bugs were fixed, it's faster too,
and does more things, just add some glue!
It does far more than print the size:
the token part's a better prize!
With each upon on a single line,
It does far more than print the size:\
the token part's a better prize!\
With each upon on a single line,\
how many things can you design?
Included is a keyword sorter,
de-obfuscator, freq reporter.
With code produced as little parts,
Included is a keyword sorter,\
de-obfuscator, freq reporter.\
With code produced as little parts,\
just add your own creative arts.
But first you have to figure out
the braces part, without a doubt!
And then the code - it isn't easy:
But first you have to figure out\
the braces part, without a doubt!\
And then the code - it isn't easy:\
for as else? That's rather cheesy!
The rest of it is standard fare:
expressions strange, the globals bare,
confusing symbols one and oh,
The rest of it is standard fare:\
expressions strange, the globals bare,\
confusing symbols one and oh,\
and precedence you have to know.
The keyword list was made external,
The keyword list was made external,\
because of standards change eternal.
Thus other languages can now,
Thus other languages can now,\
be counted just like C, somehow!
I hope you find this code obscure
enough to win, and thus procure
a public place for all to see
how badly I can butcher C!
I hope you find this code obscure\
enough to win, and thus procure\
a public place for all to see\
how badly I can butcher C!\
```
### Said another way....
@@ -204,7 +204,7 @@ winning entry keywords are checked first.
> An interesting aside: as might be expected, obfuscation has changed the frequency of
> keyword distribution over time. The top five for the decades:
>
>\
> 1980s 1990s 2000s 2010s
> ----- ----- ----- -----
> 94 if 532 char 375 if 254 int
@@ -271,9 +271,9 @@ sed 's/^# .*$//' | sed 's/^#//' |
* I assume you noticed the [braces][2]?
_Every brace is sacred,
Every brace is great.
If a brace is wasted,
_Every brace is sacred,\
Every brace is great.\
If a brace is wasted,\
Clang gets quite irate_.
* Keywords follow the 2010s top five, without the `if`, for interesting flow control.
2018/endoh1/README.md
+2 -2
View File
@@ -1,7 +1,7 @@
# Best tool to reveal holes
Yusuke Endoh
<https://github.com/mame/>
Yusuke Endoh\
<https://github.com/mame/>\
Mastodon: [@mame@ruby.social](https://ruby.social/@mame)
## To build:
2018/endoh2/README.md
+2 -2
View File
@@ -1,7 +1,7 @@
# Best use of python
Yusuke Endoh
<https://github.com/mame/>
Yusuke Endoh\
<https://github.com/mame/>\
Mastodon: [@mame@ruby.social](https://ruby.social/@mame)
## To build:
2018/ferguson/README.md
+13 -13
View File
@@ -1,8 +1,8 @@
# Best use of weasel words
Cody Boone Ferguson <weasel@xexyl.net>
[https://ioccc.xexyl.net](https://ioccc.xexyl.net)
[https://xexyl.net](https://xexyl.net)
Cody Boone Ferguson <weasel@xexyl.net>\
[https://ioccc.xexyl.net](https://ioccc.xexyl.net)\
[https://xexyl.net](https://xexyl.net)\
Mastodon: [@xexyl@fosstodon.org](https://fosstodon.org/@xexyl)
## To build:
@@ -166,7 +166,7 @@ monkey; I thought the monkey had it too easy: unlike his limited keyboard I have
**`isprint()`** returns non-zero except that only capital letters are included;
the file [prog.alt.c](prog.alt.c) has a slightly smaller keyboard. There are some
additional features I have added (including two Easter eggs); amongst others:
ability to change the target string and maximum length. See
ability to change the target string and maximum length. See\
**[How it works](#how)**, **[Hints](#hints)** and **[How to build](#build)** for
more details.
@@ -236,7 +236,7 @@ exist. The second to last example limitation example note (it's improved in the
final but this is relevant) they give is:
> The judges might not have a pet fish named Eric, so might want to state:
>
>\
> This entry factors integers between 1 and 2305567963945518424753102147331756070.
> Attempting to factor anything else will cause the program to insult your
> pet fish Eric, or in the case that you lack such a pet, will insult the
@@ -362,7 +362,7 @@ with the following options:
-qr5
\
3. Look at the first few lines again and compare it to the output of step \#1.
With the default string most modern systems shouldn't take much time to - given
decent parameters - come to an answer here but if necessary kill the program.
@@ -397,9 +397,9 @@ If you do one of:
./weasel "METHINKS IT IS A" "MONKEY"
./weasel METHINKS IT IS A MONKEY
```
\
It will search for **`MONKEY`** in both cases; in other words it's the last one.
If the string is too long given the value of **`S`** (see
If the string is too long given the value of **`S`** (see\
**[How to build](#build)**) it will be truncated.
If you actually do want to search for a string starting with a **`-`** you must
@@ -425,9 +425,9 @@ command line. Because of the joining of arguments this means that the first two
examples of the last set of three above are equivalent i.e. the following two
are equivalent:
-q-
-q-\
-q --
\
As for the caveat I referenced what does the following do?
```sh
@@ -662,7 +662,7 @@ people. Take the following invocations:
(1) $ echo test > test
(2) $ ./weasel test
(3) $ ./weasel < test
(4) $ cat test | ./weasel
(4) $ cat test | ./weasel\
(5) $ < test-strings.txt ./weasel
(6) $ cat | ./weasel
@@ -746,7 +746,7 @@ Skip to [Obfuscation](#obfuscation).
There is a type of input error, as I said, that might appear to be a bug. What
actually is going on though is due to a technicality on how spaces are printed
and the fact the program does not accept spaces other than a literal space
and the fact the program does not accept spaces other than a literal space\
**` `**; when a character in the string to be found isn't in the keyboard the
program prints an error message and then exits (returning 1). But since the
keyboard doesn't have **`'\n'`** if you were to type a **`'`** and send a
@@ -1141,7 +1141,7 @@ talented! :)** I do wonder if he tested that bit of C code though:
for(;P("\n"),R=;P("|"))for(e=C;e=P("_"+(*u++/
8)%2))P("|"+(*u/4)%2);
```
\
How is **`R=;`** valid? Since I don't have the context maybe there is something
I'm missing but either way it's a funny piece. It could also be for irony itself
(actually I had previously thought of somehow implementing something like that
2018/mills/README.md
+27 -27
View File
@@ -124,13 +124,13 @@ the system to look at the first partition on the first RK05 fixed disk, find
the `rkunix` file and load it. You should eventually see the following:
>boot
\
40Boot
: rk(0,0)rkunix
\
Berkeley UNIX (Rev. 2.9.1) Sun Nov 20 14:55:50 PST 1983
mem = 135872
\
CONFIGURE SYSTEM:
xp ? csr 176700 vector 254 skipped: No CSR
rk 0 csr 177400 vector 220 attached
@@ -148,8 +148,8 @@ the `rkunix` file and load it. You should eventually see the following:
vp ? csr 177500 vector 174 skipped: No autoconfig routines
lp ? csr 177514 vector 200 skipped: No CSR
Erase=^?, kill=^U, intr=^C
#
#\
\
Congratulations, you are running BSD UNIX 2.9 in single-user mode as root.
On the other hand, if you did a typo somewhere, the boot loader has probably
@@ -208,7 +208,7 @@ you should see:
@rkunix
mem = 1035
RESTRICTED RIGHTS
\
Use, duplication or disclosure is subject to
restrictions stated in Contract with Western
Electric Company, Inc.
@@ -225,7 +225,7 @@ Assuming you're more careful than that, we can try a few commands:
@rkunix
mem = 1035
RESTRICTED RIGHTS
\
Use, duplication or disclosure is subject to
restrictions stated in Contract with Western
Electric Company, Inc.
@@ -347,39 +347,39 @@ Now `ls` will work, and we can try some other things while we are here:
password: dmr
@ ln dd dmr .
@ ls
dd
system
as.s
dd\
system\
as.s\
b_readme
bi.s
bl.s
db.s
hello.b
ops.s
.
bi.s\
bl.s\
db.s\
hello.b\
ops.s\
.\
@ cat b_readme
Here is how to compile and run hello.b:
\
@ bc hello.b hello.s
@ as ops.s bl.s hello.s bi.s
I
II
ops.s
bl.s
hello.s
bi.s
ops.s\
bl.s\
hello.s\
bi.s\
@ a.out
Hello, World!
\
\
@ bc hello.b hello.s
@ as ops.s bl.s hello.s bi.s
I
II
ops.s
bl.s
hello.s
bi.s
ops.s\
bl.s\
hello.s\
bi.s\
@ a.out
Hello, World!
@
2018/poikola/README.md
+2 -2
View File
@@ -1,7 +1,7 @@
# Most stellar
Timo Poikola <ioccc2018@ig.fi>
<https://ig.fi/>
Timo Poikola <ioccc2018@ig.fi>\
<https://ig.fi/>\
<https://ig.fi/other/ioccc>
2018/yang/README.md
+1 -1
View File
@@ -1,6 +1,6 @@
# Most shifty
Don Yang
Don Yang\
<http://uguu.org/>
## To build: