Cody Boone Ferguson
af5482825c
The sections have been modified a fair amount. The Entries menu has been extended to have: Fixing entries, Updating author info, Thanks for the help. The first two were moved from FAQ and the last one from About. The rationale for these, in order: entries and authors have to do with entries and most of the help involves entries. It also has to do with website but in 'about' it does not seem the right place, unless maybe it is renamed to 'Credits' or something (I am not suggesting this one way or the other). This one is debatable but that was the rationale. The Status menu has been extended to have: Markdown guidelines and Security policy. The rationale is that the markdown guidelines are part of contest guidelines and the security policy is about the status of the entries and how if there are any security problems they will not be addressed (instead of about the IOCCC). The FAQ was extended to have: Compiling entries, Running entries, How to help. The reason to not have compiling and running entries under Entries is because this is 'how to' and also the menu was too long. How to help seems like a good idea under FAQ too (was in About). About was extended to have the new 'about.html' page (from about.md). This is a rare case where a new file is useful as it fits under 'About'. The menu now is: Home page, About the IOCCC, The Judges, Contact us. I was pondering the 'About [the IOCCC]' at the top and also naming it 'About us' but it seemed like a link to index.html was necessary and as for 'about us' it seemed less clear as to whether it was about the judges or the contest itself. The FAQ has been updated slightly for this. After further inspection the bin/index.html and the inc/index.html links were removed from the about section. With these changes, renaming an item or slight reordering notwithstanding, I believe that #2006 is probably in good shape.
To build:
make all
A smaller version, originally called zsmall.c (and still exists as such, as
the source of the alternate code), of applin.c, can be found in
applin.alt.c. Your machine may have an easier time with this
program. See the Alternate code section below for details.
Try:
./applin
Alternate code:
As noted above a smaller version can be used in case your cpp has a hard time
with this entry.
Alternate build:
make alt
Use applin.alt as you would applin above.
History about the smaller version:
Way back in 1988 ..
This entry took 75 minutes to compile on a Amdahl 5980-300E (a 55658
Dhyrstone/sec/cpu machine) using the System V cpp. (The GNU cpp when defined as
BIG_CPP took only 45 seconds.)
Your cpp may not be able to compile it due to a common bug that results in
cpp running out of space. The alternate code
zsmall is a smaller version
of the entry applin.c.
Judges' remarks:
This entry is by far the most unusual abuse of the C preprocessor that we have received thus far. Nearly all of the real work is done in the C preprocessor!
When we compiled applin.c on an
Amdahl 5890-300E, we found that it
spent over 75 minutes in the System V C preprocessor! Besides showing that the
standard System V cpp is slow, it showed that it contained a memory usage
problem. The applin.c only uses 29 different preprocessor symbols
(besides stdio.h) and yet the preprocessor ran out of space!
The GNU C preprocessor took under 45 seconds to perform the 2nd pass
on the Amdahl 5890-300E. But due to the ANSI-likeness of GNU cpp (v. 1-21),
it was not able to cleanly substitute a symbol that began with a '#'.
Clearly the GNU C preprocessor is faster.
Author's remarks:
No remarks were provided by the author.