From dcae40297d85d65d6d70df3c818eb765743af241 Mon Sep 17 00:00:00 2001 From: Cody Boone Ferguson <53008573+xexyl@users.noreply.github.com> Date: Sun, 20 Oct 2024 16:05:12 -0700 Subject: [PATCH 1/2] Update so-called JSON spec link in guidelines --- next/guidelines.html | 4 ++-- next/guidelines.md | 4 ++-- 2 files changed, 4 insertions(+), 4 deletions(-) diff --git a/next/guidelines.html b/next/guidelines.html index 783c75a71..502f65cf2 100644 --- a/next/guidelines.html +++ b/next/guidelines.html @@ -426,7 +426,7 @@ writing by contacting the judges.

IOCCC Guidelines version

-These IOCCC guidelines are version 28.16 2024-10-17. +These IOCCC guidelines are version 28.17 2024-10-20.

IMPORTANT: Be SURE to read the IOCCC rules.

@@ -1409,7 +1409,7 @@ Even so, we do not recommend you try and submit a JSON parser due to the fact it will likely exceed the source code size limit and because you likely can’t beat flex or bison in obfuscation. This isn’t to -say that the so-called JSON spec is not +say that the so-called JSON spec is not obfuscated, but unless you have some really clever way to compact and obfuscate a JSON parser more than flex and bison you will likely not win, either diff --git a/next/guidelines.md b/next/guidelines.md index 9033e14e6..c11fc2031 100644 --- a/next/guidelines.md +++ b/next/guidelines.md @@ -50,7 +50,7 @@ writing by [contacting the judges](../contact.html).

-These [IOCCC guidelines](guidelines.html) are version **28.16 2024-10-17**. +These [IOCCC guidelines](guidelines.html) are version **28.17 2024-10-20**.

**IMPORTANT**: Be **SURE** to read the [IOCCC rules](rules.html). @@ -1273,7 +1273,7 @@ Even so, we do not recommend you try and submit a JSON parser due to the fact it will likely exceed [the source code size limit](rules.html#rule2) and because you likely can't beat [flex](https://github.com/westes/flex) or [bison](https://www.gnu.org/software/bison/) in obfuscation. This isn't to -say that [the so-called JSON spec](https://www.json.org/json-en.html) is not +say that [the so-called JSON spec](https://github.com/xexyl/jparse/blob/master/json_README.md#so-called-json-spec) is not obfuscated, but unless you have some really clever way to compact and obfuscate a JSON parser more than [flex](https://github.com/westes/flex) and [bison](https://www.gnu.org/software/bison/) you will likely not win, either From 4e9b4db634069d9910a95db618e5fe3d658c0107 Mon Sep 17 00:00:00 2001 From: Cody Boone Ferguson <53008573+xexyl@users.noreply.github.com> Date: Sun, 20 Oct 2024 16:09:42 -0700 Subject: [PATCH 2/2] Typo fix in guidelines --- next/guidelines.html | 2 +- next/guidelines.md | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/next/guidelines.html b/next/guidelines.html index 502f65cf2..00e43a51e 100644 --- a/next/guidelines.html +++ b/next/guidelines.html @@ -1519,7 +1519,7 @@ is a hint. :-)

We RECOMMEND you put a reasonable amount effort into the content of the -remarks.md file: it is a required for for a reason. :-) +remarks.md file: it is a required for a reason. :-)

diff --git a/next/guidelines.md b/next/guidelines.md index c11fc2031..8baa769fe 100644 --- a/next/guidelines.md +++ b/next/guidelines.md @@ -1398,7 +1398,7 @@ is a **hint**. :-)

We **RECOMMEND** you put a reasonable amount effort into the content of the -`remarks.md` file: it is a required for for a reason. :-) +`remarks.md` file: it is a required for a reason. :-)