Re: The Case for Rust (in any system)

On 9/6/24 04:25, Poul-Henning Kamp wrote:
> --------
> David Chisnall writes:
>> On 6 Sep 2024, at 08:25, Poul-Henning Kamp<phk@phk.freebsd.dk>  wrote:
>>> I will also note that almost all the blame for C's current status
>>> lies with the standardization efforts, which almost seem hell-bent
>>> on destroying the language rather than improving it.
>> As someone who is involved with C++ standardisation and so periodically hears
>> things from WG14, my impression is that the people who care about the things
>> that you list have all moved to C++, […]
> ...
> In one experiment, I wrapped the C-code in:
>
> 	#ifdef __cplusplus
> 	extern "C" {
> 	#endif
>
> and compiled it with a C++ compiler.
>
> Given that we have tried to dial code quality to 11 in Varnish, the
> number of relevant observations by the C++ compiler was a devastating
> indictment of how badly the C language has been let down by it's
> stewards.
>
> I'm not saying FreeBSD should think along the same lines, but FreeBSD
> should totally think along those same lines:
>
> Even if we stick with pure C-code, the C++ std-people have a much
> more sane approach to it's proper compilation that the C std-people.
>
> And there are nice features in C++ which do not make the source code
> unreadable.
>
Second this.

Not surprised...

I have done this as long as C++ as been around and it always made for 
better code in the end.

Truly, this is one of the easy things that could be done with FreeBSD 
code, and probably would help quite a bit improving the code.

Jan