add missing news about the contest status change
This commit is contained in:
1 parent
3d9355e1c2
commit
9dd70f0fc9
6 files changed
+44
-41
No files matched your search
@@ -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.</p>
|
||||
<p>One should restrict libcurses to portable features found on BSD
|
||||
or Linux curses.</p>
|
||||
<p><a href="rules.html#rule13">Rule 13</a> states any C source that fails to compile because of unescaped
|
||||
octets with the high bit set (octet value >= 128) <strong>might</strong> be rejected.
|
||||
Instead of unescaped octets, you should use or escapes:</p>
|
||||
<pre><code>
|
||||
/* 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");</code></pre>
|
||||
<p class="leftbar">
|
||||
<a href="rules.html#rule13">Rule 13</a> no longer discourages the use of UTF-8
|
||||
characters in C code.
|
||||
</p>
|
||||
<p class="leftbar">
|
||||
It is a very good idea to, in your <code>remarks.md</code> file, tell us why you
|
||||
think your submission is obfuscated. This is particularly true if
|
||||
|
||||
Reference in new issue
Block a user