On 10/06/2025 18:43, Christopher Bazley wrote:
Hi David,
On 10/06/2025 14:19, David Brown wrote:
On 10/06/2025 10:43, Jakub Jelinek wrote:
On Tue, Jun 10, 2025 at 09:52:42AM +0200, David Brown via Gcc wrote:
So while correcting the mistakes of the past is either very slow or
impossible, we ca
Hi David,
On 10/06/2025 14:19, David Brown wrote:
On 10/06/2025 10:43, Jakub Jelinek wrote:
On Tue, Jun 10, 2025 at 09:52:42AM +0200, David Brown via Gcc wrote:
So while correcting the mistakes of the past is either very slow or
impossible, we can avoid them in the future. Consistent paramete
On 10/06/2025 10:43, Jakub Jelinek wrote:
On Tue, Jun 10, 2025 at 09:52:42AM +0200, David Brown via Gcc wrote:
So while correcting the mistakes of the past is either very slow or
impossible, we can avoid them in the future. Consistent parameter order
makes code clearer and neater, and should be
On 10/06/2025 10:17, LIU Hao wrote:
在 2025-6-10 15:52, David Brown via Gcc 写道:
On 09/06/2025 12:13, Andreas Schwab wrote:
On Jun 09 2025, Chris Bazley via Gcc wrote:
C is a language that allows considerable latitude in where things
are placed:
static int volatile p;
volatile int s
On Tue, Jun 10, 2025 at 09:52:42AM +0200, David Brown via Gcc wrote:
> So while correcting the mistakes of the past is either very slow or
> impossible, we can avoid them in the future. Consistent parameter order
> makes code clearer and neater, and should be encouraged.
If the clauses are proper
在 2025-6-10 15:52, David Brown via Gcc 写道:
On 09/06/2025 12:13, Andreas Schwab wrote:
On Jun 09 2025, Chris Bazley via Gcc wrote:
C is a language that allows considerable latitude in where things are placed:
static int volatile p;
volatile int static q;
C23 says (6.11.5 Storage-cl
On 09/06/2025 12:13, Andreas Schwab wrote:
On Jun 09 2025, Chris Bazley via Gcc wrote:
C is a language that allows considerable latitude in where things are placed:
static int volatile p;
volatile int static q;
C23 says (6.11.5 Storage-class specifiers):
The placement of a st
On Jun 09 2025, Chris Bazley via Gcc wrote:
> C is a language that allows considerable latitude in where things are placed:
>
> static int volatile p;
> volatile int static q;
C23 says (6.11.5 Storage-class specifiers):
The placement of a storage-class specifier other than at the
ired in this case.
HTH,
Chris
From: Gcc on behalf of JeanHeyd
Meneide via Gcc
Sent: 05 June 2025 20:25
To: GCC Development
Cc: Jakub Jelinek; Joseph Myers
Subject: [ C Frontend / Preprocessor ] Embed Preprocessor Parameter Order
Hi Everyone,
The C and
JeanHeyd Meneide via Gcc writes:
[...]
> While the following 2 invocation of `#embed` are identical and produce
> exactly the same data:
>
> -
> #embed clang::offset(1) limit(3) /* ONE */
> #embed limit(3) clang::offset(1) /* TWO */
> -
>
> some people questioned whether or not the di
On Thu, Jun 05, 2025 at 09:25:11PM +0200, JeanHeyd Meneide wrote:
> The C and C++ Compatibility Study Group, when working on the new
> standard `#embed` preprocessor parameter that mirrors the
> `clang::offset(...)` and `gnu::offset(...)` parameters, had someone
> raise a concern that the order of
Hi Everyone,
The C and C++ Compatibility Study Group, when working on the new
standard `#embed` preprocessor parameter that mirrors the
`clang::offset(...)` and `gnu::offset(...)` parameters, had someone
raise a concern that the order of may be confusing. The concerns came
from the June 4th, 2025
12 matches
Mail list logo
