From 9dd70f0fc9757045d1825b20cc383fdc3e45a8d8 Mon Sep 17 00:00:00 2001 From: Landon Curt Noll Date: Mon, 30 Dec 2024 13:12:49 -0800 Subject: [PATCH] add missing news about the contest status change --- news.html | 35 +++++++++++++++++++++-------------- news.md | 11 +++++++++++ next/guidelines.html | 13 ++++--------- next/guidelines.md | 16 ++++------------ next/rules.html | 5 ++--- next/rules.md | 5 ++--- 6 files changed, 44 insertions(+), 41 deletions(-) diff --git a/news.html b/news.html index c12090234..7532fc6a3 100644 --- a/news.html +++ b/news.html @@ -432,7 +432,12 @@ major events such as the opening of a new IOCCC, or who won.

FAQ on “Mastodon” for more information on Mastodon.

News

-

2024-12-28

+

2024-12-30

+

The IOCCC Rule 13 no longer discourages the +use of UTF-8 in C source. Since the days of -std=gnu17 compilers, +UTF-8 characters do not impose a compiler problem. The related guideline +states that “Rule 13 no longer discourages the use of UTF-8 +characters in C code”.

+

2024-12-28

Good News Everyone! :-)

After a 4 year effort by a number of people, with over 6168+ commits, the Great Fork Merge has been completed @@ -455,10 +460,12 @@ or fix known bugs in IOCCC winning entries.

IOCCC28 is starting!

The IOCCC28, the 40th anniversary of the IOCCC is now scheduled to run from 2024-12-29 23:58:13.213455 UTC to 2025-04-01 23:29:31.374143 UTC!!!.

+

The contest status as been changed to “pending” +and status.json has been updated to reflect this new status.

Proposed and tentative IOCCC rules and IOCCC guidelines have been released.

See FAQ Section 0 for more information on how to enter.

-

2024-06-08

+

2024-06-08

We continue to make good progress on the temp-test-ioccc website via the temp-test-ioccc repo.

@@ -488,7 +495,7 @@ not having to look at them more than once on a whole, other than possible entries that have to be added at the end, like the example below.

Once the submit server server is ready another FAQ will be added and that entry can be looked at alone.

-

2024-05-30

+

2024-05-30

A number of issues from minor fixes have been applied to the temp-test-ioccc website via the temp-test-ioccc repo.

@@ -523,7 +530,7 @@ ask for beta testing of the new IOCCC registration process and This will speed up the start date of IOCCC28.

It is our plan that IOCCC28 will occur in 2024, the 40th anniversary of the IOCCC.

-

2024-04-30

+

2024-04-30

The website now is viewing by mobile devices such as cell phones and tablets. Devices with a screen resolution 1024 pixels and narrower are given a hamburger-style menu icon in place of @@ -545,7 +552,7 @@ files that are static (not generated bin tools) report no warnings, nor info** messages, changes involving fixing invalid links to local files have been corrected, and changes involving the topbar are now HTML 5 conforming.

-

2024-04-20

+

2024-04-20

Nearly all of the temp-test-ioccc website website has undergone editorial review. Nearly all IOCCC winning entries compile on modern systems and many have try.sh scripts to help you run them. @@ -563,10 +570,10 @@ glaring “dancing bears” and other frivolous web features.

where the contents of the temp-test-ioccc website will be merged into the Official IOCCC website.

Stay tuned!

-

2024-02-29

+

2024-02-29

We continue to make good progress on website. In the temp-test-ioccc GitHub repo we have made nearly 4600 changes to date!

All web pages, including this one, are now constructed from markdown files and/or JSON data files using tools found in the bin directory.

-

2023-05-22

+

2023-05-22

We have been busy preparing for an important / significant update to this website. In the temp-test-ioccc GitHub repo we have made nearly 2645 changes to date.

While you are free to look at the temp-test-ioccc GitHub repo, please do not link to it as this repo and related website will disappear once the main @@ -622,7 +629,7 @@ that needs urgent fixing. The IOCCCMOCK will us to beta-test the new IOCCC process without putting the hard work of those who submit real IOCCC entries at risk.

Stay tuned!

-

2023-01-30

+

2023-01-30

We added to the status.json page, a “status_date” JSON member whose value is the date @@ -634,7 +641,7 @@ a “latest_news” JSON member whose value is the date of the most recent news item.

    "status_date" : "Mon Jan 30 02:28:44 PST 2023",
     "latest_news" : "Mon Jan 30 02:28:44 PST 2023"
-

2022-12-18

+

2022-12-18

As per the suggestion of Toni Mikkola (@Virtaava@home.social) we now maintain a status.json page on this website.

@@ -652,7 +659,7 @@ The details of such additional JSON members are TBD.

Instead you will have to rely on the additional JSON information and/or read the IOCCC news, and/or follow us on Mastodon via @ioccc@fosstodon.org.

-

2022-11-29

+

2022-11-29

We are planning to abandon our IOCCC Twitter feed in favor of our new IOCCC Mastodon feed.

@@ -687,7 +694,7 @@ is made possible by volunteers, and those who voluntarily support the cost of their server.

Stay tuned in Mastodon as we update you on our progress towards the next IOCCC!

-

2022-11-19

+

2022-11-19

Source code has been released for version 0.8.1 2022-11-19 of the mkiocccentry repo, a GitHub repo that includes the official iocccsize tool, @@ -699,13 +706,13 @@ to upload the above mentioned compressed tarball: when the contest is open of co judges will go through the motions (without judging the content) of an IOCCC: testing the above mentioned tools and testing the submit server.

We are working on complete rebuild of this website as well.

-

2022-01-15

+

2022-01-15

Source code has been released for version 0.24 2022-01-15 of the mkiocccentry tool, a tool that is based on, and is containing, the official iocccsize tool, will form a compressed tarball that a registered IOCCC contestant will upload to the submit server (when the contest is open of course).

-

2021-12-27

+

2021-12-27

The Judges are continuing to work on re-tooling how we run the IOCCC. We are writing tools under various repositories our @@ -714,7 +721,7 @@ We are writing tools under various repositories our Sorry for the delay, but we think you will appreciate the re-tooling when it is completed. Stay tuned!

-

2021-10-21

+

2021-10-21

The Judges are re-tooling how we run the IOCCC. Our goal is to build a smoother, more rapid process centered around diff --git a/news.md b/news.md index eb790c5fb..2feea148e 100644 --- a/news.md +++ b/news.md @@ -14,6 +14,14 @@ for more information on Mastodon. +## 2024-12-30 + +The IOCCC [Rule 13](next/rules.html#rule13) no longer discourages the +use of UTF-8 in C source. Since the days of `-std=gnu17` compilers, +UTF-8 characters do not impose a compiler problem. The related guideline +states that "Rule 13 no longer discourages the use of UTF-8 +characters in C code". + + ## 2024-12-28 ### Good News Everyone! :-) @@ -45,6 +53,9 @@ or fix [known bugs in IOCCC winning entries](bugs.html). The IOCCC28, the [40th anniversary of the IOCCC](faq.html#ioccc_start) is now scheduled to run from **2024-12-29 23:58:13.213455 UTC** to **2025-04-01 23:29:31.374143 UTC**!!!. +The [contest status](status.html) as been changed to "**pending**" +and [status.json](status.json) has been updated to reflect this new status. + Proposed and tentative [IOCCC rules](next/rules.html) and [IOCCC guidelines](next/guidelines.html) have been released. diff --git a/next/guidelines.html b/next/guidelines.html index 733191add..ebdca44c7 100644 --- a/next/guidelines.html +++ b/next/guidelines.html @@ -1679,15 +1679,10 @@ their entries. In some cases tools have a “Save As” option that will prevent such trailing control-M’s being added.

One should restrict libcurses to portable features found on BSD or Linux curses.

-

Rule 13 states any C source that fails to compile because of unescaped -octets with the high bit set (octet value >= 128) might be rejected. -Instead of unescaped octets, you should use or escapes:

-

-              /* 123456789 123456789 123456789 123456 */
-    char *foo = "This string is 36 octets in length \263";
-          /* This octet requires 4 octets of source ^^^^ */
-    if (strlen(foo) == 36) printf("foo is 36 octets plus a final NUL\n");
-    else printf("This code should not print this message\n");
+

+Rule 13 no longer discourages the use of UTF-8 +characters in C code. +

It is a very good idea to, in your remarks.md file, tell us why you think your submission is obfuscated. This is particularly true if diff --git a/next/guidelines.md b/next/guidelines.md index fddbca690..0a0abdda2 100644 --- a/next/guidelines.md +++ b/next/guidelines.md @@ -1560,18 +1560,10 @@ prevent such trailing control-M's being added. One should restrict libcurses to portable features found on BSD or Linux curses. -[Rule 13](rules.html#rule13) states any C source that fails to compile because of unescaped -octets with the high bit set (octet value >= 128) **might** be rejected. -Instead of unescaped octets, you should use \octal or \hex escapes: - -``` - - /* 123456789 123456789 123456789 123456 */ - char *foo = "This string is 36 octets in length \263"; - /* This octet requires 4 octets of source ^^^^ */ - if (strlen(foo) == 36) printf("foo is 36 octets plus a final NUL\n"); - else printf("This code should not print this message\n"); -``` +

+[Rule 13](rules.html#rule13) no longer discourages the use of UTF-8 +characters in C code. +

It is a very good idea to, in your `remarks.md` file, tell us why you diff --git a/next/rules.html b/next/rules.html index d95c7b1d9..95fcae1ea 100644 --- a/next/rules.html +++ b/next/rules.html @@ -462,7 +462,7 @@ writing by contacting the judges.

Jump to: top

-These IOCCC rules are version 28.15 2024-12-28. +These IOCCC rules are version 28.16 2024-12-29.

The markdown form of these rules @@ -852,8 +852,7 @@ their rule abuse is legal, in the remarks.md file.

Rule 13

-Any C source that fails to compile because of unescaped octets with -the high bit set (octet value >= 128) might be rejected. +7 out of 13 UTF-8 characters in C code agree that this rule number is lucky enough to be a prime number.

Jump to: top

diff --git a/next/rules.md b/next/rules.md index 34dbfcff1..05d96105a 100644 --- a/next/rules.md +++ b/next/rules.md @@ -55,7 +55,7 @@ Jump to: [top](#)

-These [IOCCC rules](rules.html) are version **28.15 2024-12-28**. +These [IOCCC rules](rules.html) are version **28.16 2024-12-29**.

@@ -604,8 +604,7 @@ Jump to: [top](#)

-Any C source that fails to compile because of unescaped octets with -the high bit set (octet value >= 128) **_might_** be rejected. +7 out of 13 UTF-8 characters in C code agree that this rule number is lucky enough to be a prime number.