What can be learned from studying long gone development practices?

Re:What can be learned from studying long gone development p... by m_mueller on Monday August 16, 2021 @05:15AM (#28196268)

obviously, as long as the language is turing complete, but you just converted an unstructured program to a structured one.

[ Parent | on HN ]

Re:What can be learned from studying long gone development p... by lmm on Monday August 16, 2021 @08:32AM (#28197287)

To the same extent, and in the same way, as you did when you converted a state machine the same way? I still don't get what distinction you're drawing between state machine style and GOTO style.

[ Parent | on HN ]

Re:What can be learned from studying long gone development p... by maskros on Monday August 16, 2021 @08:09AM (#28197125)

And gained nothing except more verbose syntax. The goto spaghetti is still spaghetti whether you use "goto" or "switch".

[ Parent | on HN ]

Re:What can be learned from studying long gone development p... by m_mueller on Monday August 16, 2021 @03:00PM (#28201568)

Disagree. You eliminate backward gotos except for the while loop, which is much more clearly communicating the way to extend the code (by adding more states or state transitions) to the next person taking over. I‘m not categorically against goto in certain contexts (like C based systems programming), but IMO backwards jumps with goto need to be eliminated.

[ Parent | on HN ]