Landon Curt Noll
0bc6c3e413
We quasi-canonicalized markdown links to FAQ entries. **IMPORTANT NOTE**: This is a useful step in completing issue #2417. This commit is consistent with the top level TODO comment requirements. Nevertheless, this changes made by this commit needs to be examined and in some cases improved. A link to an FAQ entry is of the form: ``` FAQ on "[the link text](....faq.html#string)" FAQ on "[the link text](....faq.html#string)" ``` The "FAQ" is at the start of the line, or in rare cases is preceded only by whitespace. The reference to the FAQ starts outside of the markdown link with the string **FAQ ON "**. After the markdown link is a **"** followed by either the end of line or a single punctuation character such as a period or comma. We reduced the size of "the link text" that refer to an FAQ to at most 3 words. In some cases the sentence and/or text surrounding the markdown link to a FAQ may need to be further adjusted to better accommodate this new style. **IMPORTANT NOTE**: References to a FAQ entry are on a separate line. p.s. When linking to the `faq.html` file itself, we use markdown of the form "`the [IOCCC FAQ](..../faq.html)`" and place the word "the" outside of the "IOCCC FAQ" link text. Given the above system (and because references to an FAQ entry is on a separate line), the following command shows links to FAQ entries, sorted by FAQ entry "link #name" so that one may evaluate the way a given FAQ entry is referenced: ```sh find * -name '*.md' -print0 | xargs0 grep -E '^[[:space:]]*FAQ on "' | sed -e 's/^\([^:]*\):\( *FAQ on "[^#]*\)#\([^)]*\)\()".*\)$/#\3\t\1\t\2#\3\4/' | sort ``` The above command shows the value of consistency when it comes to FAQ references. **NOTE**: There are a few differences on how a given FAQ is references. That is probably OK as there is NOT an "total mandate" that all references to a given FAQ must have the same "link text" for example. On the other hand if references to a given FAQ can be identical, that might be helpful. We are certain that in some contexts the "link text" might need to change. Should we decide to change the way FAQ are referenced, we will be able to modify identify and modify them with greater ease.' Examine the changes made by this commit and adjust and/or improve as needed. Performed `make www` to accomplish the above and to test under macOS.
3.7 KiB
THIS IS AN EXPERIMENTAL IOCCC WEBSITE
IMPORTANT: This is NOT the official IOCCC website!
Please visit www.ioccc.org for the official IOCCC web.
Please do NOT bookmark nor link to this experimental website!
When this experiment is finished, this site will go away!
This test web tree is part of the temp-test-ioccc GitHub repo.
This website will be undergoing major changes, so expect many broken links, typos and other problems. If you wish to recommend changes (understanding that things may be rapidly changing out from under your copy), then consider making pull requests against the temp-test-ioccc GitHub repo.
What follows is the actual index.html file
Suggestions for visitors
Explore, under the Entries in the topbar menu:
- Winning Entries
- People who have won
- Other parts of the IOCCC menu
If you see this icon 
in the upper right corner, click on it to display the menu.
On a touchscreen mobile device browser wider than 1024 pixels, press and hold the menu you wish to activate (in the upper right corner) in order to activate the pull-down. If this does not work or you prefer to use a plaintext menu even with JavaScript enabled, you can do so here. See also the FAQ on "website menus".
Obfuscate defined:
tr.v. -cated, -cating, -cates.
1a. To render obscure.
1b. To darken.
2. To confuse: his emotions obfuscated his judgment.
[LLat. obfuscare, to darken : ob(intensive) + Lat. fuscare,
to darken < fuscus, dark.] -obfuscation n. obfuscatory adj.
Goals of the Contest
The goals of the IOCCC:
- To write the most Obscure/Obfuscated C program within the rules.
- To show the importance of programming style, in an ironic way.
- To stress C compilers with unusual code.
- To illustrate some of the subtleties of the C language.
- To provide a safe forum for poor C code. :-)
Entering the Contest
View the current status of the IOCCC to see of the IOCCC is open for submissions.
See FAQ on "how to submit" for more information.
Important Disclaimer
IOCCC code is for educational and entertainment purposes only. We do NOT recommend installing any winning IOCCC entry code. Use code found the IOCCC repo and in the IOCCC web site at your own risk!
The IOCCC and the IOCCC judges DISCLAIM ALL WARRANTIES WITH REGARD TO THIS SOFTWARE, INCLUDING ALL IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THEY BE LIABLE FOR ANY SPECIAL, INDIRECT OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE.