Landon Curt Noll
b66c79254a
When language is specified in a markdown code block such as:
````
```c
printf("Hello, world!\n");
```
````
is used, the resulting HTML as produced by `pandoc(1)` combined
with our revised `ioccc.css` is not intent the code block well.
A temporary "_hack-a-round_" is to turn the "markdown code language
specifier" into an HTML comment. For example:
````
```<!---c-->
printf("Hello, world!\n");
```
````
This commits turns off existing markdown code language specifiers
for now, while preserving our ability to restore them in the future
when a better "_hack-a-round_" to the "markdown code language
specifier" problem is found.
The HTML impact if this "_hack-a-round_" is to produce HTML that
looks like this:
```
<pre class="<!---c-->"><code> .. </code></pre>
```
We might be able to create a complex set of classes for each markdown
code language (there won't be very many) in `ioccc.css`, or we might
find a more general CSS (or maybe `pandoc(1)`?) solution.
For now, this hack-a-round will have to do.
To build:
make chaos
NOTE: Some systems do not implement halfdelay() in their libcurses.
You might try compiling with -lncurses if you have that library.
Or you can build this entry without the halfdelay() call by:
make chaos_nohalf
To use:
./chaos
Try:
./try.sh
This script will run the program on each data file. To quit the program hit q.
If not all files have been used it will go to the next one; otherwise the script
will be finished. To end the script early send intr/ctrl-c.
The script will give you instructions on how to use the program and things to try each time it is run, as a helpful reminder.
Judge's Comments:
This is the author's first IOCCC entry. We thought the entry was a nice example of a compact collection of obfuscations.
Can you figure out why, in some cases, it wants to read itself?
Author's remarks:
Usage
The executable takes a single argument for the data file to use. If no argument is given, it will find a data file by itself, don't worry about it...
Summary
This is a simple ncurses 3D object viewer. The keys y, u, i,
h, j, and k rotate. a and z zoom in and out. q quits.
Given about 3 seconds of no input, it will start rotating until
interrupted by user input.
Features (aka Bugs):
Memory malloc(3)ed is never freed. This shouldn't be a big deal,
since only one block is ever allocated, and the OS should recover it.
My local flavor of lint doesn't seem to like the fact that I never
return from main(). Feh, what does it know? Otherwise, ignoring
lint's over protectiveness ("Of course I'm not using all of the
functions defined in curses.h!"), it's lint clean.
If the compiler happens to generate the byte sequence "AlWuzEre" in the executable by chance, the program may be unable to locate the embedded string. As a result, running the program without an external data file may act in undefined ways.
If the compiler doesn't store char * P's data in a nice contiguous
stream, it would be bad. As above, it would break running the
program without an external data file.
If the incoming data is corrupt, the results are undefined. (Although dumping core is a popular result.)
When a point passes behind the camera, it is still plotted. The object will "bounce" off the camera, but the result (some points in front, some reflected from the rear) looks really odd. And it sometimes hangs. So just don't fly through objects. You'll be happier.