Hi Linus, On Mon, Jul 07, 2025 at 01:49:20PM -0700, Linus Torvalds wrote: > On Mon, 7 Jul 2025 at 13:29, Alejandro Colomar <a...@kernel.org> wrote: > > > > I am in the C Committee, and have proposed this API for standardization. > > I have a feeling that the committee might be open to it. > > Honestly, how about fixing the serious problems with the language instead?
I'm doing some work on that. See the new _Countof() operator? That was my first introduction in the standard, last year. I'm working on an extension to it that I believe will make array parameters safer. > Get rid of the broken "strict aliasing" garbage. I don't feel qualified to comment on that. > Get rid of the random "undefined behavior" stuff that is literally > designed to let compilers intentionally mis-compile code. We're indeed working on that. The last committee meeting removed a large number of undefined behaviors, and turned them into mandatory diagnostics. And there's ongoing work on removing more of those. > Because as things are, "I am on the C committee" isn't a > recommendation. It's a "we have decades of bad decisions to show our > credentials". I joined in 2024 because I was fed up with the shit they were producing and wanted to influence it. You don't need to convince me. > In the kernel, I have made it very very clear that we do not use > standard C, because standard C is broken. I agree. I personally use GNU C and tend to ignore the standard. But I'm still working on improving the standard, even if just to avoid having to learn Rust (and also because GCC and glibc don't accept any improvements or fixes if they don't go through the standard, these days). Have a lovely day! Alex > I stand by my "let's not add random letters to existing functions that > are already too confusing". > > Linus -- <https://www.alejandro-colomar.es/>
signature.asc
Description: PGP signature
