Files
ioccc/1987/wall
Landon Curt Noll f29b37e49a improve HTML menus, add social.html, prep for IOCCC28 winners
Prepare for the winners of **IOCCC28**.

> However these are not the 2024 droids you are looking for.  :-)

The HTML menu (both JavaScript and non-JavaScript) has been updated.

The `Status -> Rules and guidelines' have been replaced with two
separate menus `Status -> IOCCC rules` and `Status -> IOCCC guidelines`.

Added a new top level `social.html` page: built from a new `social.md`.

Sorted rules for building specific web pages in the top level `Makefile`.
Added `make social` to make the `social.html` page from `social.md`.

The `bin/gen-top-html.sh` now is able to process a argument of **social**
to process the new top level `social.html` page.

Changed `bin/gen-top-html.sh` VERSION from "2.0.0 2025-03-13"
to "2.0.1 2025-07-25".

Below `About -> Home page` a new `About -> IOCCC social media` menu item
as added.

Because the menu change touched every HTML file, we changed the general
copyright date range for HTML files from "1984-2024" to "1984-2025"
due to the extensive changes made for **IOCCC28**.

Those markdown files that were modified in 2025 had their copyright date
range also changed from "1984-2024" to "1984-2025".

Rebuilt tarballs and sitemap due to the extensive HTML rebuilding.

Ran `make update` to perform the above.
2025-07-26 13:06:29 -07:00
..
2023-09-11 05:53:18 -07:00
2023-07-06 21:49:38 -07:00

To build:

    make all
    ```


## To use:

``` <!---sh-->
    ./wall
    # enter some numbers

    ./wall | some_command
    # enter some strings or numbers, depending on command

Try:

    ./try.sh

You may of course run the commands manually and enter text as you wish. For instance you might try one or both of:

    ./wall | bc

    ./wall | cat

and enter some input like:

    x*x
    2^x
    quit # for the cat version

which the script does through a pipeline except that here you can enter more text if you wish, line by line.

Judges' remarks:

What we found amazing was how the flow of control was transferred between subroutines. Careful inspection will show that the array of pointers to functions named vi refers to functions which seem to not be directly called. Even so, these pointers to functions are being used as an argument to signal(3) (used both with and without an arg - but how?). Can you determine why this is being done and how it is being exploited?

Some compilers complained about this file, so we changed: =++I to = ++I.

Author's remarks:

No remarks were provided by the author.