From: Florian Weimer <fweimer@redhat.com>
To: Gerald Pfeifer <gerald@pfeifer.com>
Cc: gcc-patches@gcc.gnu.org
Subject: Re: [PATCH] Notes on the warnings-as-errors change in GCC 14
Date: Thu, 15 Feb 2024 17:49:34 +0100 [thread overview]
Message-ID: <87y1bl8yg1.fsf@oldenburg.str.redhat.com> (raw)
In-Reply-To: <9fce9298-1aec-27ce-591e-a1d415d34dba@pfeifer.com> (Gerald Pfeifer's message of "Sat, 10 Feb 2024 00:07:45 +0100 (CET)")
* Gerald Pfeifer:
> On Fri, 2 Feb 2024, Florian Weimer wrote:
>> +<h3 id="warnings-as-errors">Certain warnings are now errors</h3>
>
> That's quite a nice description, thank you, Florian!
>
>> +The initial ISO C standard and its 1999 revision removed support for
>
> May I suggest to wrap paragraphs in <p>...</p>? Not strictly necessary any
> more, now that we switched to HTML 5, though more consistent and explicit.
I've tried this now, and adds extra whitespace in some cases, for
example here:
“
<p>
In most cases, simply adding the missing <code>int</code> keyword
addresses the error. For example, a flag variable like
</p>
<pre>
static initialized;
</pre>
<p>
becomes:
</p>
<pre>
static <ins>int</ins> initialized;
</pre>
”
I would have to nest the <pre> in the <p>, which suggests a complexity
that just isn't there.
Thanks,
Florian
next prev parent reply other threads:[~2024-02-15 16:49 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-02 16:59 Florian Weimer
2024-02-02 18:08 ` Jonathan Wakely
2024-02-15 15:57 ` Florian Weimer
2024-02-02 19:06 ` Jonathan Wakely
2024-02-08 7:04 ` Sam James
2024-02-15 16:07 ` Florian Weimer
2024-02-15 16:20 ` Sam James
2024-02-09 23:07 ` Gerald Pfeifer
2024-02-15 16:22 ` Florian Weimer
2024-02-15 22:58 ` Gerald Pfeifer
2024-02-15 16:49 ` Florian Weimer [this message]
2024-02-10 11:00 ` Gerald Pfeifer
2024-02-15 16:44 ` Florian Weimer
2024-02-16 21:23 ` Gerald Pfeifer
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87y1bl8yg1.fsf@oldenburg.str.redhat.com \
--to=fweimer@redhat.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=gerald@pfeifer.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).