uecker

This is certainly not true. Accessing bytes of objects is well-defined in C.

The issue is that a programmer is allowed to declare a function on its own without including the header, but then a function aliasing feature would not be visible and does not help. But if we waived …

Lot of stawman arguments.

Not every high-level language gives you byte-level access to the representation of memory objects. But it is also wrong to reduce a language to what is in the spec.

The mechanism actually does not solve the problem it claims to solve.

It is a simple counterexample to your incorrect statement.

Have your mind blown: https://godbolt.org/z/xnn3PPxvW

This discussion was about C not C++. GCC also has language extensions for safety, such as the access attribute, the dynamic object size pass, and far better warnings. Big tech cares about a lot of thi…

IMHO gcc has better warnings and support for safety. Industry mostly wants a BSD-licensed toolchain. I could not care less.

It is usually assumed that it does not control the callee and the jump has to preserve the calling convention for a call.

If you care about C, use gcc.

Easy and still expressive, so you can map many things to C. And while the language standard does not define an ABI it takes a lot of care not to require any ABI break.

You can do more with less energy, if you use it more efficiently, which sometimes may be more cost effective compared to producing more. Electricity consumption peaked in Germany in 2007 and is down …

Your understanding of this is poor. First, the same is true with neighbors putting renewables on the grid, it is not just Germany having renewables anymore. But the issue is not that the "grid go…

I certainly also remember the kernel crashing, but this was in the 90s. Later perhaps once or twice on faulty hardware. Shell, I don't think I have seen this ever.

How does "emergency-dumping" create cost to neighbors? But what you miss is that most of the EU now has a lot of renewables.

This seems too low by an order of magnitude. In 2021, nuclear power produced 69 TWh in Germany. For comparison, renewables produced 240 TWh in 2021 and 292 TWh in 2025. But I agree with your general p…

Germany invested in renewables already at a time when they were very expensive. This created an economy of scale that brought prices down to everybody. Nuclear was never economical anywhere, so no, Ge…

People who did this found renewables to be cost effective.

The difference is that Germany's investments in renewables at a time when they were still expensive helped to create an economy of scale, which brought down prices for everyone and helped trigger…

Russia did not completely cut gas exports to Europa, but reduced in substantially, but this was a reaction to sanctions and the decision in Europa to reduce imports from Russia (but more slowly). In f…

But it did exactly this. The pipeline was not the only way to import Russian gas.

Can you explain what you mean exactly regarding this augmenting this syntax?

That was discussed, but consistency with sizeof was considered more important. And if you figured out how to parse sizeof, parsing countof is not an additional burden.

Sorry, that others are equally bad is not an excuse, and also not that Rust's design makes it more difficult to package. Either you care about security or you don't.

Basically all C programs I use, shells, editors, terminals, etc. But I do not claim that there "never has been a memory-related bug" but that it is not "riddled with" memory-relat…

It had no crash during 30 years, not after 30 years.

Those style guides would also disallow having multiple declarators in a single declaration.

I would say a modern style of C using proper abstractions and modern tooling is less prone to memory safety issues than C written in the style of C89.

If I would add another array, it would look like: int c_style_array[2][5][3]; There is also no jumping back and forth. C declarations are also recursively constructed. One can complain about the irreg…