Fix some missed edge cases of Un\*x to Unix
.. and there very well could be more.
This commit is contained in:
Cody Boone Ferguson committed
1 parent
73fc551f70
commit
e74f1c4837
8 files changed
+38
-50
No files matched your search
+28
-36
@@ -8,7 +8,7 @@ on how to compile it and how to run the winning program.
|
||||
Look at the winning source and try to figure how it does what it does!
|
||||
You may then wish to look at the Author's remarks for even more details.
|
||||
|
||||
Use make to compile entries. It is possible that on non-Un\*x / non-Linux
|
||||
Use make to compile entries. It is possible that on non-Unix / non-Linux
|
||||
systems the makefile needs to be changed. See the Makefile for details.
|
||||
|
||||
Read over the makefile for compile/build issues. Your system may
|
||||
@@ -20,48 +20,45 @@ yours is lacking, you may need to compile using gcc instead of your
|
||||
local compiler.
|
||||
|
||||
|
||||
New Judge
|
||||
---------
|
||||
## New Judge
|
||||
|
||||
The judges were unable to contact Jeremy Horn for judging the 2000 contest.
|
||||
|
||||
As a result, Simon Cooper:
|
||||
|
||||
http://www.sfik.com/
|
||||
As a result, Simon Cooper: <http://www.sfik.com/>
|
||||
|
||||
joined our team. Simon is well known for being a co-author of the 2nd
|
||||
edition of the Building Internet Firewalls book.
|
||||
|
||||
|
||||
Remarks on some of the entries
|
||||
------------------------------
|
||||
## Remarks on some of the entries
|
||||
|
||||
There were some outstanding entries that did not win. Unfortunately
|
||||
some very good entries lost because they:
|
||||
|
||||
+ depended too much on non-portable side effects in expressions;
|
||||
+ depended too much on a particular byte order;
|
||||
+ required the use of a special script, data file or pseudo-machine
|
||||
language that was not supplied with the entry.
|
||||
- depended too much on non-portable side effects in expressions;
|
||||
- depended too much on a particular byte order;
|
||||
- required the use of a special script, data file or pseudo-machine language
|
||||
that was not supplied with the entry.
|
||||
|
||||
We hope the authors of some of those entries will fix and re-submit
|
||||
them for the next IOCCC.
|
||||
|
||||
We believe you will be impressed with this year's winners. The
|
||||
Best of Show is a fine example of compact obfuscation. But don't
|
||||
ignore the shorter winners. The Best Small Program, Best Abuse of
|
||||
User and Most Complete Program are well worth studying in detail.
|
||||
We believe you will be impressed with this year's winners. The [Best of
|
||||
Show](jarijyrki/README.md) is a fine example of compact obfuscation. But don't
|
||||
ignore the shorter winners. The [Best Small Program](natori/README.md), [Best
|
||||
Abuse of User](briddlebane/README.m) and [Most Complete Program](tomx/README.md)
|
||||
are well worth studying in detail.
|
||||
|
||||
The Worst Abuse of the Rules is technically allowed by the rules.
|
||||
We gave it an award this year, but don't assume you can get away
|
||||
with using it next time ... :-)
|
||||
The [Worst Abuse of the Rules](dlowe/README.md) is technically allowed by the
|
||||
rules. We gave it an award this year, but don't assume you can get away with
|
||||
using it next time ... :-)
|
||||
|
||||
Speaking of time, be sure to check out the Astronomically Obfuscated
|
||||
and the Most Timely Output.
|
||||
Speaking of time, be sure to check out the [Astronomically
|
||||
Obfuscated](rince/README.md) and the [Most Timely
|
||||
Output](schneiderwent/README.md).
|
||||
|
||||
|
||||
There was no 1999 contest
|
||||
-------------------------
|
||||
## There was no 1999 contest
|
||||
|
||||
So what happened to 1999? Landon Curt Noll was scheduled to take a
|
||||
vacation from the IOCCC this year. The remaining judges were
|
||||
@@ -77,38 +74,33 @@ It was decided that the 15th contest would be the year 2000 contest
|
||||
scheduled start of the contest). That is why there is no 1999 contest.
|
||||
|
||||
|
||||
|
||||
Final Comments
|
||||
--------------
|
||||
## Final Comments
|
||||
|
||||
Please send us comments and suggestions what we have expressed above.
|
||||
Also include anything else that you would like to see in future contests.
|
||||
Send such email to:
|
||||
|
||||
questions@ioccc.org
|
||||
```
|
||||
questions@ioccc.org
|
||||
```
|
||||
|
||||
If you use, distribute or publish these entries in some way, please drop
|
||||
us a line. We enjoy seeing who, where and how the contest is used.
|
||||
|
||||
You must include the words ``ioccc question'' in the subject of your email
|
||||
You must include the words 'ioccc question' in the subject of your email
|
||||
message when sending email to the judges.
|
||||
|
||||
If you have problems with any of the entries, AND YOU HAVE A FIX, please
|
||||
email the fix (patch file or the entire changed file) to the above address.
|
||||
|
||||
The next IOCCC is planned to start towards early spring 2001. Watch:
|
||||
|
||||
https://www.ioccc.org/
|
||||
The next IOCCC is planned to start towards early spring 2001. Watch: <https://www.ioccc.org/>
|
||||
|
||||
for news of the next contest.
|
||||
|
||||
=-=
|
||||
|
||||
p.s. The has been mentioned in an Amici Curiae for the DeCSS case. See:
|
||||
|
||||
http://cryptome.org/mpaa-v-2600-bac.htm
|
||||
|
||||
and seach on the word ioccc (twice).
|
||||
p.s. The above has been mentioned in an Amici Curiae for the DeCSS case. See
|
||||
<http://cryptome.org/mpaa-v-2600-bac.htm> and search on the word ioccc (twice).
|
||||
|
||||
=-=
|
||||
|
||||
|
||||
+4
-8
@@ -1,8 +1,6 @@
|
||||
2001 marked the "The Sixteenth International Obfuscated C Code Contest"
|
||||
# 2001 marked the "The Sixteenth International Obfuscated C Code Contest"
|
||||
|
||||
|
||||
Standard IOCCC stuff
|
||||
--------------------
|
||||
## Standard IOCCC stuff
|
||||
|
||||
Look at the README.md file for the given winning entry for information
|
||||
on how to compile it and how to run the winning program.
|
||||
@@ -10,11 +8,9 @@ Look at the winning source and try to figure how it does what it does!
|
||||
You may then wish to look at the Author's remarks for even more details.
|
||||
|
||||
The IOCCC has a web site and now has a number of international mirrors. The
|
||||
primary site can be found at,
|
||||
primary site can be found at <https://www.ioccc.org>.
|
||||
|
||||
https://www.ioccc.org
|
||||
|
||||
Use make to compile entries. It is possible that on non-Un\*x / non-Linux
|
||||
Use make to compile entries. It is possible that on non-Unix / non-Linux
|
||||
systems the makefile needs to be changed. See the Makefile for details.
|
||||
|
||||
Read over the makefile for compile/build issues. Your system may
|
||||
|
||||
+1
-1
@@ -15,7 +15,7 @@ The primary site can be found at,
|
||||
|
||||
> <https://www.ioccc.org/>
|
||||
|
||||
Use make to compile entries. It is possible that on non-Un\*x / non-Linux
|
||||
Use make to compile entries. It is possible that on non-Unix / non-Linux
|
||||
systems the makefile needs to be changed. See the Makefile for details.
|
||||
|
||||
This year we included most of the information included by the submitters
|
||||
|
||||
+1
-1
@@ -15,7 +15,7 @@ The primary site can be found at,
|
||||
|
||||
> <https://www.ioccc.org/>
|
||||
|
||||
Use make to compile entries. It is possible that on non-Un\*x / non-Linux
|
||||
Use make to compile entries. It is possible that on non-Unix / non-Linux
|
||||
systems the makefile needs to be changed. See the Makefile for details.
|
||||
|
||||
This year we included most of the information included by the submitters
|
||||
|
||||
+1
-1
@@ -15,7 +15,7 @@ The primary site can be found at,
|
||||
|
||||
> <https://www.ioccc.org/>
|
||||
|
||||
Use make to compile entries. It is possible that on non-Un\*x / non-Linux
|
||||
Use make to compile entries. It is possible that on non-Unix / non-Linux
|
||||
systems the makefile needs to be changed. See the Makefile for details.
|
||||
|
||||
Read over the makefile for compile/build issues. Your system may require
|
||||
|
||||
+1
-1
@@ -13,7 +13,7 @@ The primary IOCCC web site can be found at,
|
||||
|
||||
> <https://www.ioccc.org/>
|
||||
|
||||
Use make to compile entries. It is possible that on non-Un\*x / non-Linux
|
||||
Use make to compile entries. It is possible that on non-Unix / non-Linux
|
||||
systems the makefile needs to be changed. See the Makefile for details.
|
||||
|
||||
Look at the source and try to figure out what the programs do, and run
|
||||
|
||||
+1
-1
@@ -14,7 +14,7 @@ The primary IOCCC web site can be found at,
|
||||
|
||||
> <https://www.ioccc.org/>
|
||||
|
||||
Use make to compile entries. It is possible that on non-Un\*x / non-Linux
|
||||
Use make to compile entries. It is possible that on non-Unix / non-Linux
|
||||
systems the makefile needs to be changed. See the Makefile for details.
|
||||
|
||||
Read over the makefile for compile/build issues. Your system may require
|
||||
|
||||
+1
-1
@@ -12,7 +12,7 @@ The primary IOCCC web site can be found at,
|
||||
|
||||
> <https://www.ioccc.org/>
|
||||
|
||||
Use make to compile entries. It is possible that on non-Un\*x / non-Linux
|
||||
Use make to compile entries. It is possible that on non-Unix / non-Linux
|
||||
systems the makefile needs to be changed. See the Makefile for details.
|
||||
|
||||
Read over the makefile for compile/build issues. Your system may require
|
||||
|
||||
Reference in new issue
Block a user