Update so-called JSON spec link in guidelines
This commit is contained in:
1 parent
74deedb0fd
commit
dcae40297d
2 files changed
+4
-4
No files matched your search
@@ -426,7 +426,7 @@ writing by <a href="../contact.html">contacting the judges</a>.</p>
|
||||
<h2 id="ioccc-guidelines-version">IOCCC Guidelines version</h2>
|
||||
</div>
|
||||
<p class="leftbar">
|
||||
These <a href="guidelines.html">IOCCC guidelines</a> are version <strong>28.16 2024-10-17</strong>.
|
||||
These <a href="guidelines.html">IOCCC guidelines</a> are version <strong>28.17 2024-10-20</strong>.
|
||||
</p>
|
||||
<p><strong>IMPORTANT</strong>: Be <strong>SURE</strong> to read the <a href="rules.html">IOCCC rules</a>.</p>
|
||||
<div id="change_marks">
|
||||
@@ -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 <a href="rules.html#rule2">the source code size limit</a>
|
||||
and because you likely can’t beat <a href="https://github.com/westes/flex">flex</a> or
|
||||
<a href="https://www.gnu.org/software/bison/">bison</a> in obfuscation. This isn’t to
|
||||
say that <a href="https://www.json.org/json-en.html">the so-called JSON spec</a> is not
|
||||
say that <a href="https://github.com/xexyl/jparse/blob/master/json_README.md#so-called-json-spec">the so-called JSON spec</a> is not
|
||||
obfuscated, but unless you have some really clever way to compact and
|
||||
obfuscate a JSON parser more than <a href="https://github.com/westes/flex">flex</a> and
|
||||
<a href="https://www.gnu.org/software/bison/">bison</a> you will likely not win, either
|
||||
|
||||
+2
-2
@@ -50,7 +50,7 @@ writing by [contacting the judges](../contact.html).
|
||||
</div>
|
||||
|
||||
<p class="leftbar">
|
||||
These [IOCCC guidelines](guidelines.html) are version **28.16 2024-10-17**.
|
||||
These [IOCCC guidelines](guidelines.html) are version **28.17 2024-10-20**.
|
||||
</p>
|
||||
|
||||
**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
|
||||
|
||||
Reference in new issue
Block a user