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

Fix html files for 2012

Browse Source
This commit is contained in:
Cody Boone Ferguson committed 2024-10-13 17:56:59 -07:00
1 parent 1dffd99226
commit b13b36b46a
6 files changed
+89 -101
Download Patch File Download Diff File Expand all files Collapse all files

No files matched your search

bugs.md
+41 -48
View File
@@ -3365,10 +3365,8 @@ fire](https://en.wikipedia.org/wiki/Halt_and_Catch_Fire_(computing)) :
The author stated:
```
If there is a division by zero, square-root of a negative number, or similar
operation, then the results are undefined.
```
> If there is a division by zero, square-root of a negative number, or similar
operation, then the results are undefined.
<div id="2012_deckmyn">
@@ -3381,34 +3379,31 @@ The author stated:
The author stated:
```
The memory locations of `argv` are used for various purposes. Therefore, the
program name (default `deckmyn`) must be *at least 4 characters long*, including
possibly the path. This, along with the ending `'\0'`, gives a minimum 5 bytes of
useful memory space. Otherwise, the program may attempt to write outside the
string.
The code is quite sensitive. Errors in the input can lead to strange results.
The code does not read beyond the end of the music input, but that is about the
only error checking available. Any input that is not according to the rules in
the deckmyn.html, may cause errors.
The program has no special hardware limitations or requirements, other than 8bit
`char` (`signed` or `unsigned`) and two's complement negatives.
The limitations of using `char` as counters for e.g. the number of music staves
are minor. 127 staves to a page is rather a lot.
The file layout must be exactly the same as deckmyn.c though, only the locations
of space (`" "`) may differ.
Every element in the music is given by a string of *exactly* 3 characters. Any
violation of this will result in the rest of the music being interpreted in some
randomly wrong way. Notice that in a file, the newline is also a character!
Therefore, when preparing music in a file, care should be taken that the last
musical element of a line is only 2 characters!
```
> The memory locations of `argv` are used for various purposes. Therefore, the
program name (default `deckmyn`) must be *at least 4 characters long*, including
possibly the path. This, along with the ending `'\0'`, gives a minimum 5 bytes
of useful memory space. Otherwise, the program may attempt to write outside the
string.
>
> The code is quite sensitive. Errors in the input can lead to strange
results. The code does not read beyond the end of the music input, but that is
about the only error checking available. Any input that is not according to the
rules in the deckmyn.html, may cause errors.
>
> The program has no special hardware limitations or requirements, other than
8bit `char` (`signed` or `unsigned`) and two's complement negatives.
>
> The limitations of using `char` as counters for e.g. the number of music
staves are minor. 127 staves to a page is rather a lot.
>
> The file layout must be exactly the same as deckmyn.c though, only the
locations of space (`" "`) may differ.
>
> Every element in the music is given by a string of *exactly* 3 characters.
Any violation of this will result in the rest of the music being interpreted in
some randomly wrong way. Notice that in a file, the newline is also a character!
Therefore, when preparing music in a file, care should be taken that the last
musical element of a line is only 2 characters!
The manual referred to is [here](2012/deckmyn/deckmyn.html).
@@ -3441,22 +3436,20 @@ The author stated:
The author stated:
```
If the input doesn't start with a valid program, that is,
if the interpreter reaches end-of-file during program parsing,
it will crash in some way. E.g. the following might dump core:
echo -n "U" | ./tromp
Furthermore, the interpreter requires the initial encoded lambda term to be closed,
that is, variable n can only appear within at least 'n' enclosing lambdas.
For instance, here the term '\ 5' is not closed, causing the interpreter to crash when
looking into a null-pointer environment:
echo ">Hello, world" | ./tromp
will likely dump core.
```
> If the input doesn't start with a valid program, that is, if the interpreter
reaches end-of-file during program parsing, it will crash in some way. E.g. the
following might dump core:
>
> `echo -n "U" | ./tromp`
>
> Furthermore, the interpreter requires the initial encoded lambda term to be
closed, that is, variable n can only appear within at least 'n' enclosing
lambdas. For instance, here the term `'\ 5'` is not closed, causing the
interpreter to crash when looking into a null-pointer environment:
>
> `echo ">Hello, world" | ./tromp`
>
> will likely dump core.
<div id="2012_vik">