News for hackers. Stuff that matters.

A comment on C++26: Trivial infinite loops are no longer undefined behaviour. Parent comment

Re:C++26: Trivial infinite loops are no longer undefined beh... by otabdeveloper4 on Saturday September 19, 2026 @02:57AM (#49764055)
> Since they are invisibly inserted

They're not, all destructors are explicit. Seems like a skill issue on your end.

[ Parent | on HN ]
Re:C++26: Trivial infinite loops are no longer undefined beh... by WalterBright on Saturday September 19, 2026 @03:26AM (#49764206)
Since AFAIK I'm still the only person to write a correct C++ (C++98) compiler from preprocessor to object file, I know all about destructors.

Here's a fun one for your amusement:

    foo(a, b, c);
The parameters are pass by value. a, b and c are objects that have destructors. Have a look at the code generated for that.

It is nice that the compiler does the dirty work for you, but the various paths with exceptions and recovery with invisible code may not be well tested.

[ Parent | on HN ]
Re:C++26: Trivial infinite loops are no longer undefined beh... by degaart on Sunday September 20, 2026 @02:05AM (#49772906)
> Seems like a skill issue on your end.

You're talking to walter bright, the guy who wrote the digital mars C++ compiler

[ Parent | on HN ]
Re:C++26: Trivial infinite loops are no longer undefined beh... by otabdeveloper4 on Monday September 21, 2026 @12:03AM (#49782931)
> appeal to authority

Okay.

[ Parent | on HN ]