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

moved and improved thanks

Browse Source 
Moved thanks-for-fixes.md -> thanks-for-help.md

References to thanks-for-help.md are referred to
as just the _thanks file_.

Updated links to reflect the above file change.

Links to winner files in bugs.md now start with /.

Updated the `/inc/sidenav.default.html` file
to use an improved sidenav menu that includes
a link to "How to enter the IOCCC".

Fixed reference to FAQ entry regarding 'gets()' in `bugs.md`.

Removed some trailing whitespace in `bugs.md`.
Removed some trailing whitespace in `faq.md`.

Fixed links into specific thanks file entries.

Added more info to FAQ 0.0 "How may I submit to the IOCCC?".

The temporary top level HTML files (contact.html, index.html,
judges.html, news.html, winners.html, years.html) have
a consistent set of links (w/o any bold links) that
match the revised `/inc/sidenav.default.html` sidenav menu.
These temporary top level HTML files are not yet being built
and so they do not yet use the `inc/*.html` system.

TODO: Turn contact.html, index.html, judges.html, news.html, winners.html,
and years.html into markdown files that markdown to HTML tools will generate.

NOTE: Trying to resolve a GitHub pull request conflict.  *sigh*
This commit is contained in:
Landon Curt Noll committed 2023-12-07 19:02:31 -08:00
1 parent ddf5746d4e
commit 6805d14c80
11 files changed
+654 -611
Download Patch File Download Diff File Expand all files Collapse all files

No files matched your search

1988/dale/README.md
+1 -1
View File
@@ -44,7 +44,7 @@ make clobber alt
```
Use `dale.alt` as you would `dale` above. To understand the differences in more
detail, see [thanks-for-fixes.md](/thanks-for-fixes.md).
detail, see [thanks-for-help.md](/thanks-for-help.md).
## Judges' remarks:
bugs.md
+28 -26
View File
@@ -20,10 +20,11 @@ request](https://github.com/ioccc-src/temp-test-ioccc/pulls) (with ONE PULL
REQUEST *PER* FIX, please)!
We will be **happy to credit anyone who submits successful [GitHub pull
requests](https://github.com/ioccc-src/temp-test-ioccc/pulls)** in the [thanks
file](thanks-for-fixes.md). If you're a previous winner we will add a link to your winning
entries in the file (if you're not a previous winner we can add a link to your
GitHub page or personal website if you have one, should you wish).
requests](https://github.com/ioccc-src/temp-test-ioccc/pulls)** in the
[thanks](/thanks-for-help.md) file. If you're a previous winner we will
add a link to your winning entries in the file (if you're not a previous
winner we can add a link to your GitHub page or personal website if you
have one, should you wish).
If you do fix an entry please feel free to delete the entry from this file!
Otherwise if you wish to not worry about it we can do that to make sure the
@@ -632,13 +633,14 @@ also have `abba` which the original code does not!
Now notice how the `avnz` in the first line got changed to `niam`, its ROT13
value. Notice also how some of these are in comments!
`main()` is in there somewhere and that had to be changed to call `pain()` (see
the [entry in the thanks file](/thanks-for-fixes.md#1989westley-readmemd) for
details on how as this was not as straight forward as it is for other entries)
as well. Now if you notice on that line you have in a comment `niam`. If you
were to change that to `niap` (pain backwards) that function would end up as
`pain()` in generated code! That's assuming that it's just the reversal version,
of course but ver1 is the ROT13 version.
`main()` is in there somewhere and that had to be changed to call
`pain()` (see the [thanks](/thanks-for-help.md#1989_westley)
file (see the _1989/westley_ section for details on how as this was
not as straight forward as it is for other entries) as well. Now
if you notice on that line you have in a comment `niam`. If you
were to change that to `niap` (pain backwards) that function would
end up as `pain()` in generated code! That's assuming that it's
just the reversal version, of course but ver1 is the ROT13 version.
These facts are bad enough but then you throw in the reverse of it without ROT13
and then another version that has the reversal _and_ ROT13 then you can see it's
@@ -830,22 +832,21 @@ entry itself. Can you fix the actual entry? You are welcome to try and do so.
### STATUS: uses gets() - change to fgets() if possible
### Source code: [1992/gson/gson.c](1992/gson/gson.c)
### Information: [1992/gson/README.md])1992/gson/README.md_
### Information: [1992/gson/README.md])(1992/gson/README.md)
Cody changed it so that the buffer size is `ARG_MAX+1` to try and get past the
problem of `gets()` being used in a more complex way.
It would be ideal if it were to use `fgets()` though. This will probably be
looked at later but you're welcome to try and fix this too! A tip on how
`gets()` is being used is in the [thanks-for-fixes.md](thanks-for-fixes.md)
file.
`gets()` is being used is in the [FAQ](/faq.md#gets) file.
## 1992 kivinen
### STATUS: known bug - please help us fix
### Source code: [1992/kivinen/kivinen.c](1992/kivinen/kivinen.c)
### Information: [1992/kivinen/README.md])1992/kivinen/README.md_
### Information: [1992/kivinen/README.md](1992/kivinen/README.md)
When you start the program everything starts to move over to the right side and
then ends. [Yusuke Endoh](/winners.html#Yusuke_Endoh) pointed out that if you
@@ -1122,7 +1123,7 @@ pit room you will end up dying even though you didn't explicitly move there.
### Information: [1994/ldb/README.md](1994/ldb/README.md)
[Cody Boone Ferguson](/winners.html#Cody_Boone_Ferguson) fixed this to compile
with modern systems (see the [thanks-for-fixes.md](thanks-for-fixes.md) file for
with modern systems (see the [thanks](/thanks-for-help.md) file for
what had to change) but the entry also used `gets()` which in some systems would
print out a warning along with the output of the program. Naturally it could
also overflow long lines. Cody changed it to `fgets()` to prevent the display
@@ -1575,7 +1576,7 @@ see that it does indeed crash!
The reason for this not working is really strange.
```sh
$ echo "7 P 6 d P P 8 p" | ./dlowe
$ echo "7 P 6 d P P 8 p" | ./dlowe
7668
$ echo "7 P 6 d P P 8 p" | ./dlowe | grep 7
$
@@ -1613,7 +1614,7 @@ $
```
Well this explains why the `tr` does not transliterate it to `poot` but why is
this happening? Why can't it be redirected to another file even?
this happening? Why can't it be redirected to another file even?
If it could be figured out why it's not writing to stdout and yet at the same
time is writing to stdout one bug could be fixed. Maybe it's the perl messing
@@ -1700,7 +1701,7 @@ To not get 'unimplemented' you can remove from the perl:
```perl
sub AUTOLOAD { print"unimplemented\n"}
sub AUTOLOAD { print"unimplemented\n"}
```
(Note that the author stated this was used for exception handling so another
@@ -1867,7 +1868,7 @@ explicitly stated that it requires i386 linux.
There I found what should be a more portable version which is included as
[otccelf.c](2001/bellard/otccelf.c) (after adding some `#include`s and the
modification by Yusuke noted in the [thanks-for-fixes.md](/thanks-for-fixes.md)
modification by Yusuke noted in the [thanks](/thanks-for-help.md)
file) but it appears this *also* requires i386 linux; indeed looking at the code
it hard codes paths that are i386 specific to linux.
@@ -2009,7 +2010,7 @@ identified by `R`.
Since the game never ends properly the score is not printed either.
It appears that the crash happens in more than one place. For instance it has
happened at
happened at
```c
XCheckMaskEvent(d, 4,&e)
@@ -2028,7 +2029,7 @@ In both cases the pointer `d` was corrupted:
(Display *) 0x0000000000000001
```
It is believed that it also happened at
It is believed that it also happened at
```c
XDrawString(d,w,g,W/3,H/2,m,B);
@@ -3239,9 +3240,10 @@ There was no IOCCC in 2023.
We hope this document was of use to you in determining which entries are known
to have a problem, what entries are known to have features that are not bugs and
so on. We also thank you for going through this document and, if you propose any
[fixes](/thanks-for-fixes.md) via a [GitHub pull
fixes via a [GitHub pull
request](https://github.com/ioccc-src/temp-test-ioccc/pulls) or otherwise, we
thank you as well for the help! We will happily add you to the
[thanks](/thanks-for-help.md) file.
There was no IOCCC in these years.
@@ -3256,8 +3258,8 @@ completed.
We hope this document was of use to you in determining which entries are known
to have a problem, what entries are known to have features that are not bugs and
so on. We also thank you for going through this document and, if you propose any
[fixes](/thanks-for-fixes.md) via a [GitHub pull
so on. We also thank you for going through this document and, if you propose any
fixes] via a [GitHub pull
request](https://github.com/ioccc-src/temp-test-ioccc/pulls) or otherwise, we
thank you as well for the help! We will happily add you to the
[thanks-for-fixes.md](/thanks-for-fixes.md) file as well.
[thanks](/thanks-for-help.md) file as well.
contact.html
+12 -8
View File
@@ -13,18 +13,22 @@ Contest </I></FONT></CENTER><BR>
<P>
<CENTER>
<A HREF="judges.html">The judges</A> |
<A HREF="index.html">IOCCC home page</A> |
<A HREF="faq.html">FAQ</A> |
<A HREF="index.html#enter">How to enter</A> |
<B>Contacting the IOCCC</B>
<A HREF="years.html">Winning entries</A> |
<A HREF="winners.html">People who have won</A>
<BR><BR>
<A HREF="news.html">IOCCC News</a> |
<A HREF="faq.html#submit">How to enter the IOCCC</A> |
<A HREF="faq.html">FAQ</A>
<BR><BR>
<A HREF="bugs.md">Known Bugs &amp; (Mis)features</A> |
<A HREF="thanks-for-fixes.md">Thanks for the fixes</A>
<A HREF="faq.html#fix_a_winner">Fixing IOCCC winners</A> |
<A HREF="faq.html#fix_web_site">Fixing the web site</A> |
<A HREF="faq.html#fix_author">Fixing winner info</A> |
<A HREF="thanks-for-help.md">Thanks for the help</A>
<BR><BR>
<A HREF="index.html#news">IOCCC news</A> |
<A HREF="winners.html">People who have won</A> |
<A HREF="years.html">Winning entries</A>
<A HREF="judges.html">The judges</A> |
<A HREF="contact.html">Contacting the IOCCC</A>
</CENTER>
<HR>
faq.md
+32 -13
View File
@@ -1,7 +1,7 @@
# FAQ Table of Contents
## Section 0 - [Submitting entries to a new IOCCC](#faq0)
- [0.0 - How do I submit my entry to the IOCCC?](#faq0_0)
- [0.0 - How may I submit to the IOCCC?](#faq0_0)
- [0.1 - What types of entries have been over-submitted to the IOCCC?](#faq0_1)
- [0.2 - What should I put in my entry's Makefile?](#faq0_2)
- [0.3 - May I use a different source or compiled filename than prog.c or prog?](#faq0_3)
@@ -70,9 +70,11 @@ other inconsistencies with the original entry?](#faq4_3)
## <a name="faq0"></a>Section 0: Submitting entries to a new IOCCC
### <a name="faq0_0"></a><a name="submit"></a>FAQ 0.0: How do I submit my entry to the IOCCC?
### <a name="faq0_0"></a><a name="submif"></a>FAQ 0.0: How may I submit to the IOCCC?
0. Verify that for submissions.
To submit your code to the IOCCC, you **MUST** follow these steps:
0. Verify that the IOCCC is open for submissions
Check the [status.json](status.json) URL and
check the [IOCCC news](news.html#news) to
@@ -81,16 +83,25 @@ see of the IOCCC is open.
You may only register for the IOCCC
and you may only submit your entries to the IOCCC when the IOCCC is **OPEN**.
1. Register for the IOCCC
1. Read the latest IOCCC rules and review the IOCCC guidelines
Please read any pay close attention to the [official IOCCC rules](/rules.html).
You are also **highly encouraged** to review the
[official IOCCC guidelines](/guidelines.html) as they contain important
suggestions, useful hints, and IOCCC humor. :-)
2. Register for the IOCCC
```
XXX - instructions TBD - XXX
```
Once you have been registered, you will receive an email message for how to
prepare your entries for submission, and how to upload the compressed tarballs
to our submission portal.
2. Obtain the latest mkiocccentry toolkit
3. Obtain the latest mkiocccentry toolkit
If you do not have an mkiocccentry tool directory:
@@ -108,13 +119,13 @@ git fetch
git rebase
```
3. Make the mkiocccentry toolkit
4. Make the mkiocccentry toolkit
```sh
make clobber all
```
4. Run the mkiocccentry tool to form your entry tarball
5. Run the mkiocccentry tool to form your entry tarball
```sh
./mkiocccentry work_dir prog.c Makefile remarks.md [file ...]
@@ -138,7 +149,15 @@ remarks.md Remarks about your entry in markdown format
NOTE: It is *NOT* necessary to install the tools to use them as you can run
the tools from the top of the _mkiocccentry repo_ directory just fine.
5. upload your entry to the IOCCC submit server
If `mkiocccentry` tool indicates that there is a problem with your entry,
especially if it identifies a [rule 2](/rules.html#2) related problem,
you are **strongly** encouraged to revise and correct your entry and
then re-run the `mkiocccentry` tool.
If you choose to risk of violating rules, be sure an explain your reason
for doing so in your _remarks.md_ file.
6. upload your entry to the IOCCC submit server
```
XXX - instructions TBD - XXX
@@ -764,7 +783,7 @@ for 64-bit systems. Many were fixed to work with modern systems but some are
supposed to only work with 32-bit systems so any updated version of these
entries should be an alternate version.
Other entries like [2001/herrmann2](/thanks-for-fixes.md#2001herrmann2-readmemd)
Other entries like [2001/herrmann2](/thanks-for-help.md#2001_herrmann2)
now work with 32-bit AND 64-bit systems.
Please see the [bugs.md](/bugs.md) file for the problematic entry in question to see if the problem is known, and if a fix is wanted, consider trying to port the code to a 64-bit system and submitting a pull request with that change. Pull requests that fix such code while trying to minimize the impact of any changes and preserving the spirit of the orignal code are very welcome!
@@ -1231,7 +1250,7 @@ version like `winner.alt.c` or `prog.alt.c`. In fact it is advisable to look at
the original code when reading the author's (and sometimes authors') remarks.
### <a name="faq4_1"></a>FAQ 4.1: Why were some calls to the libc function `gets(3)` changed to use `fgets(3)`?
### <a name="faq4_1"></a><a name="gets"></a>FAQ 4.1: Why were some calls to the libc function `gets(3)` changed to use `fgets(3)`?
Some may wonder: "Doesn't this tamper with the entry too much?"
@@ -1441,7 +1460,7 @@ Note that just because you have a fix does not mean it'll be accepted. This
might be because the author objects or it doesn't fit in some way or another. Of
course if the entry does not work we'll certainly be more inclined to accept the
fix. If it is accepted we'll be happy to credit you in the
[thanks](/thanks-for-fixes.md) file. If you're a previous winner we will happily
[thanks](/thanks-for-help.md) file. If you're a previous winner we will happily
link to your entries; if you're not we can link to your website if you wish.
See [FAQ 5.2](#faq5_2) for information on how to submit a fix to an IOCCC entry.
@@ -1474,7 +1493,7 @@ files and we welcome these too!
IOCCC winning entries are presented!
In any event we will happily add you to the
[thanks-for-fixes.md](/thanks-for-fixes.md) file for your help!
[thanks](/thanks-for-help.md) file for your help!
And of course, an IOCCC winner may update their own entries
(metadata as well as source code and any extra files) by opening a
@@ -1558,7 +1577,7 @@ When in doubt, consider opening up an [IOCCC issue](https://github.com/ioccc-src
See [FAQ 5.3](#faq5_3) for information on opening up an IOCCC issue.
## <a name="faq5_5"></a>FAQ 5.5: How may I correct or update IOCCC author information?
## <a name="faq5_5"></a><a name="fix_author"></a>FAQ 5.5: How may I correct or update IOCCC author information?
Authors of IOCCC winning entries are kept in JSON files of the form:
inc/sidenav.default.html
+6 -3
View File
@@ -12,17 +12,20 @@
<hr>
<div class="sidenav">
<a href="%%DOCROOT_URL_SLASH%%news.html">IOCCC News</a>
<a href="%%DOCROOT_URL_SLASH%%judges.html">The IOCCC Judges</a>
<a href="%%DOCROOT_URL_SLASH%%contact.html">Contacting the IOCCC</a>
<a href="%%DOCROOT_URL_SLASH%%faq.html#submit">How to enter the IOCCC</a>
<a href="%%DOCROOT_URL_SLASH%%faq.html">FAQ</a>
</div>
<hr>
<div class="sidenav">
<a href="%%DOCROOT_URL_SLASH%%bugs.html">Bugs &amp; (mis)features</a>
<a href="%%DOCROOT_URL_SLASH%%faq.html#fix_a_winner">Fixing IOCCC winners</a>
<a href="%%DOCROOT_URL_SLASH%%faq.html#fix_web_site">Fixing the web site</a>
<a href="%%DOCROOT_URL_SLASH%%bugs.html">Bugs &amp; (mis)features</a>
<a href="%%DOCROOT_URL_SLASH%%faq.html#fix_author">Fixing winner info</a>
<a href="%%DOCROOT_URL_SLASH%%thanks-for-fixes.html">Thanks for the fixes</a>
</div>
<div class="sidenav">
<a href="%%DOCROOT_URL_SLASH%%judges.html">The IOCCC Judges</a>
<a href="%%DOCROOT_URL_SLASH%%contact.html">Contacting the IOCCC</a>
<hr>
<div class="sidenav">
<a href="#top">Jump to top</a>
index.html
+13 -10
View File
@@ -45,19 +45,22 @@ then consider making pull requests against the
<P>
<CENTER>
<A HREF="judges.html">The judges</A> |
<B>IOCCC home page</B> |
<A HREF="faq.html">FAQ</A> |
<A HREF="contact.html">Contacting the IOCCC</A> |
<A HREF="news.html#news">IOCCC news</A>
<A HREF="index.html">IOCCC home page</A> |
<A HREF="years.html">Winning entries</A> |
<A HREF="winners.html">People who have won</A>
<BR><BR>
<A HREF="news.html">IOCCC News</a> |
<A HREF="faq.html#submit">How to enter the IOCCC</A> |
<A HREF="faq.html">FAQ</A>
<BR><BR>
<A HREF="bugs.md">Known Bugs &amp; (Mis)features</A> |
<A HREF="thanks-for-fixes.md">Thanks for the fixes</A> |
<A HREF="news.html#news">IOCCC news</A> |
<A HREF="faq.html#fix_a_winner">Fixing IOCCC winners</A> |
<A HREF="faq.html#fix_web_site">Fixing the web site</A> |
<A HREF="faq.html#fix_author">Fixing winner info</A> |
<A HREF="thanks-for-help.md">Thanks for the help</A>
<BR><BR>
<A HREF="index.html#news">IOCCC news</A> |
<A HREF="winners.html">People who have won</A> |
<A HREF="years.html">Winning entries</A>
<A HREF="judges.html">The judges</A> |
<A HREF="contact.html">Contacting the IOCCC</A>
</CENTER>
<P>
judges.html
+12 -8
View File
@@ -13,18 +13,22 @@ Contest </I></FONT></CENTER><BR>
<P>
<CENTER>
<B>The judges</B> |
<A HREF="index.html">IOCCC home page</A> |
<A HREF="faq.html">FAQ</A> |
<A HREF="index.html#enter">How to enter</A> |
<A HREF="contact.html">Contacting the IOCCC</A>
<A HREF="years.html">Winning entries</A> |
<A HREF="winners.html">People who have won</A>
<BR><BR>
<A HREF="news.html">IOCCC News</a> |
<A HREF="faq.html#submit">How to enter the IOCCC</A> |
<A HREF="faq.html">FAQ</A>
<BR><BR>
<A HREF="bugs.md">Known Bugs &amp; (Mis)features</A> |
<A HREF="thanks-for-fixes.md">Thanks for the fixes</A>
<A HREF="faq.html#fix_a_winner">Fixing IOCCC winners</A> |
<A HREF="faq.html#fix_web_site">Fixing the web site</A> |
<A HREF="faq.html#fix_author">Fixing winner info</A> |
<A HREF="thanks-for-help.md">Thanks for the help</A>
<BR><BR>
<A HREF="index.html#news">IOCCC news</A> |
<A HREF="winners.html">People who have won</A> |
<A HREF="years.html">Winning entries</A>
<A HREF="judges.html">The judges</A> |
<A HREF="contact.html">Contacting the IOCCC</A>
</CENTER>
<HR>
news.html
+14 -11
View File
@@ -45,19 +45,22 @@ then consider making pull requests against the
<P>
<CENTER>
<A HREF="judges.html">The judges</A> |
<A HREF="index.hml">IOCCC home page</A> |
<A HREF="faq.html">FAQ</A> |
<A HREF="index.html#enter">How to enter</A> |
<A HREF="contact.html">Contacting the IOCCC</A>
<A HREF="index.html">IOCCC home page</A> |
<A HREF="years.html">Winning entries</A> |
<A HREF="winners.html">People who have won</A>
<BR><BR>
<A HREF="news.html">IOCCC News</a> |
<A HREF="faq.html#submit">How to enter the IOCCC</A> |
<A HREF="faq.html">FAQ</A>
<BR><BR>
<A HREF="bugs.md">Known Bugs &amp; (Mis)features</A> |
<A HREF="thanks-for-fixes.md">Thanks for the fixes</A> |
<B>IOCCC news</B>
<A HREF="faq.html#fix_a_winner">Fixing IOCCC winners</A> |
<A HREF="faq.html#fix_web_site">Fixing the web site</A> |
<A HREF="faq.html#fix_author">Fixing winner info</A> |
<A HREF="thanks-for-help.md">Thanks for the help</A>
<BR><BR>
<A HREF="index.html#news">IOCCC news</A> |
<A HREF="winners.html">People who have won</A> |
<A HREF="years.html">Winning entries</A>
<A HREF="judges.html">The judges</A> |
<A HREF="contact.html">Contacting the IOCCC</A>
</CENTER>
<HR>
@@ -173,7 +176,7 @@ Mikkola</A> (<I>@Virtaava@home.social</I>) we now maintain a
In addition to the IOCCC-style <I>easter egg</I>, you may count on
the JSON status page having a JSON member with name of <B>"contest"</B>
that will have a value of either <B>"closed"</B> or <B>"open"</B>.
When a future <B>IOCCC</B> is announced or the IOCCC is currently open,
When a future <B>IOCCC</B> is announced or the IOCCC is currently open,
the JSON member with name of <B>"contest"</B> will change from
<B>"closed"</B> to <B>"open"</B>.
<P>
thanks-for-fixes.md → thanks-for-help.md
+512 -515
View File
File diff suppressed because it is too large. Load diff
winners.html
+12 -8
View File
@@ -13,18 +13,22 @@ Contest </I></FONT></CENTER><BR>
<P>
<CENTER>
<A HREF="judges.html">The judges</A> |
<A HREF="index.html">IOCCC home page</A> |
<A HREF="faq.html">FAQ</A> |
<A HREF="index.html#enter">How to enter</A> |
<A HREF="contact.html">Contacting the IOCCC</A>
<A HREF="years.html">Winning entries</A> |
<A HREF="winners.html">People who have won</A>
<BR><BR>
<A HREF="news.html">IOCCC News</a> |
<A HREF="faq.html#submit">How to enter the IOCCC</A> |
<A HREF="faq.html">FAQ</A>
<BR><BR>
<A HREF="bugs.md">Known Bugs &amp; (Mis)features</A> |
<A HREF="thanks-for-fixes.md">Thanks for the fixes</A>
<A HREF="faq.html#fix_a_winner">Fixing IOCCC winners</A> |
<A HREF="faq.html#fix_web_site">Fixing the web site</A> |
<A HREF="faq.html#fix_author">Fixing winner info</A> |
<A HREF="thanks-for-help.md">Thanks for the help</A>
<BR><BR>
<A HREF="index.html#news">IOCCC news</A> |
<B>People who have won</B> |
<A HREF="years.html">Winning entries</A>
<A HREF="judges.html">The judges</A> |
<A HREF="contact.html">Contacting the IOCCC</A>
</CENTER>
<CENTER><P>[
years.html
+12 -8
View File
@@ -16,18 +16,22 @@ Contest </I></FONT></CENTER><BR>
<P>
<CENTER>
<A HREF="judges.html">The judges</A> |
<A HREF="index.html">IOCCC home page</A> |
<A HREF="faq.html">FAQ</A> |
<A HREF="index.html#enter">How to enter</A> |
<A HREF="contact.html">Contacting the IOCCC</A>
<A HREF="years.html">Winning entries</A> |
<A HREF="winners.html">People who have won</A>
<BR><BR>
<A HREF="news.html">IOCCC News</a> |
<A HREF="faq.html#submit">How to enter the IOCCC</A> |
<A HREF="faq.html">FAQ</A>
<BR><BR>
<A HREF="bugs.md">Known Bugs &amp; (Mis)features</A> |
<A HREF="thanks-for-fixes.md">Thanks for the fixes</A>
<A HREF="faq.html#fix_a_winner">Fixing IOCCC winners</A> |
<A HREF="faq.html#fix_web_site">Fixing the web site</A> |
<A HREF="faq.html#fix_author">Fixing winner info</A> |
<A HREF="thanks-for-help.md">Thanks for the help</A>
<BR><BR>
<A HREF="index.html#news">IOCCC news</A> |
<A HREF="winners.html">People who have won</A> |
<B>Winning entries</B>
<A HREF="judges.html">The judges</A> |
<A HREF="contact.html">Contacting the IOCCC</A>
</CENTER>
<DIV style="margin-left:10%; margin-right:10%;" align="center"> [ <A HREF="#2020">2020</A> | <A HREF="#2019">2019</A> | <A HREF="#2018">2018</A> | <A HREF="#2015">2015</A> | <A HREF="#2014">2014</A> | <A HREF="#2013">2013</A> | <A HREF="#2012">2012</A> | <A HREF="#2011">2011</A> | <A HREF="#2006">2006</A> | <A HREF="#2005">2005</A> | <A HREF="#2004">2004</A> | <A HREF="#2001">2001</A> | <A HREF="#2000">2000</A> | <A HREF="#1998">1998</A> | <A HREF="#1996">1996</A> | <A HREF="#1995">1995</A> | <A HREF="#1994">1994</A> | <A HREF="#1993">1993</A> | <A HREF="#1992">1992</A> | <A HREF="#1991">1991</A> | <A HREF="#1990">1990</A> | <A HREF="#1989">1989</A> | <A HREF="#1988">1988</A> | <A HREF="#1987">1987</A> | <A HREF="#1986">1986</A> | <A HREF="#1985">1985</A> | <A HREF="#1984">1984</A> | <A HREF="#ALL">ALL</A> ] </DIV>