News for hackers. Stuff that matters.
Re:C++23: Removing garbage collection support by tester756 on Wednesday November 01, 2023 @02:05PM (#38102296)
>Ultimately, thankfully, it never got made into a real keyword.

Why "thankfully"?

Re:C++23: Removing garbage collection support by ska on Wednesday November 01, 2023 @02:15PM (#38102457)
canonically: https://homepages.cwi.nl/~storm/teaching/reader/Dijkstra68.p...

but see also 50+ years of back and forth on that subject, other opinions available.

Re:C++23: Removing garbage collection support by tester756 on Thursday November 02, 2023 @05:07AM (#38110779)
This paper was written in the times where goto was way more powerful than current goto, wasn't it?
Re:C++23: Removing garbage collection support by SillyUsername on Wednesday November 01, 2023 @08:39PM (#38107412)
I'm guessing you never had to debug spaghetti non OO code that used GOTO or you'd not be asking that question :D
Re:C++23: Removing garbage collection support by gugagore on Wednesday November 01, 2023 @10:54PM (#38108436)
OO is a lot of things to a lot of people, but it's not "structured control flow".
Re:C++23: Removing garbage collection support by tester756 on Thursday November 02, 2023 @05:06AM (#38110773)
What's difference between debugging spaghetti non OO code from debuggin spaghetti abused OO code?

both are terrible mess to debug, yet we aren't calling out ppl using (or even abusing) OOP

Re:C++23: Removing garbage collection support by SillyUsername on Thursday November 02, 2023 @03:02PM (#38118438)
Nothing from my POV. GOTO is more necessary (or even required) in procedural non OO languages because of fewer constructs to support modelling or structure. The OP mentioned redundant features, and in OO GOTO is redundant.