Format, typo, consistency check YYYY/README.md
There are many fixes made but a few questions remain so when I reach those years I will address those then. Unfortunately, due to infrastructure work right now, this is all I can say even though there are a number of things I'd like to say.
This commit is contained in:
1 parent
778f57b318
commit
ffdd724032
47 files changed
+326
-556
No files matched your search
+12
-25
@@ -9,22 +9,13 @@ 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. This year we included most of the
|
||||
information included by the submitter.
|
||||
|
||||
The IOCCC has a website and now has a number of international mirrors.
|
||||
The primary site can be found at [www.ioccc.org](https://www.ioccc.org).
|
||||
|
||||
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
|
||||
them with various inputs.
|
||||
|
||||
Read over the Makefile for compile/build issues. Your system may require
|
||||
certain changes (add or remove a library, add or remove a `#define`).
|
||||
|
||||
Some ANSI C compilers are not quite as good as they should be. If
|
||||
yours is lacking, you may need to compile using gcc instead of your
|
||||
local compiler.
|
||||
|
||||
The IOCCC has a website and now has a number of international mirrors.
|
||||
The primary website can be found at [www.ioccc.org](https://www.ioccc.org).
|
||||
|
||||
|
||||
## Remarks on some of the winning entries
|
||||
|
||||
@@ -66,25 +57,21 @@ and 22 (one third of 666).
|
||||
|
||||
Rule 22, now known as **Catch 22** states:
|
||||
|
||||
```
|
||||
22) Your source code, data files, remarks and program output must NOT
|
||||
identify the authors of your code. The judges STRONGLY prefer to
|
||||
not know who is submitting entries to the IOCCC.
|
||||
|
||||
The "Peter Honeyman is exempt" guideline also applies to this rule.
|
||||
Identifying yourself, in an obvious way in your code, data, remarks
|
||||
or program output, unless you are Peter Honeyman or pretending
|
||||
to be Peter Honeyman, will be grounds for disqualification of your entry.
|
||||
```
|
||||
> 22) Your source code, data files, remarks and program output must NOT identify
|
||||
> the authors of your code. The judges STRONGLY prefer to not know who is
|
||||
> submitting entries to the IOCCC.
|
||||
>
|
||||
> The "Peter Honeyman is exempt" guideline also applies to this rule.
|
||||
> Identifying yourself, in an obvious way in your code, data, remarks or program
|
||||
> output, unless you are Peter Honeyman or pretending to be Peter Honeyman, will
|
||||
> be grounds for disqualification of your entry.
|
||||
|
||||
A number of other entries were based on [iocccsize.c](%%REPO_URL%%/2015/iocccsize.c), making
|
||||
derivative works rather than original works.
|
||||
|
||||
Still other entries were too large, violating the first line of rule 2:
|
||||
|
||||
```
|
||||
2) The size of your program source must be <= 4096 bytes in length.
|
||||
```
|
||||
> 2) The size of your program source must be <= 4096 bytes in length.
|
||||
|
||||
While these entries might have passed under the 2053 limit for iocccsize,
|
||||
they were larger than <= 4096 bytes, sometimes by an order or magnitude.
|
||||
|
||||
Reference in new issue
Block a user