They played us absolute fools. intmain() is the only function ever needed aside from loops, if you can’t implement what you need, then your project is of the devil.
Loops don’t get labels. Labels are awesome. Sprinkle in some goto so you can use labels.
In languages like python inside a loop you have if condition: continue. Except continue means don’t continue, you skip to the next iteration without breaking the loop. That’s confusing as heck (and what is else doing on loops Guido???). if condition: gotoloop is more honest.
I also like that goto is “take my stack frame and run that procedure instead”, which is kind of unique and cool in its own way, and impossible to do with most lexical scoping systems. It’s reliable zero cost function calling (if you can make your optimizer happy).
Everyone loves repeating “goto considered harmful” and “numbering should start at zero”, but nobody critically thinks about those things. Rules are made to be broken.
~Oh, and the numbering argument is totally wrong… using one notation to advocate for another is silly. Offset from zero, but index by domain logic!~
The problem is that it’s easy to make code that is LESS readable; in order to prevent horrible unmaintainable spaghetti, it is forbidden nearly everywhere. A lot of coding ‘rules’ are really just ways to try to cut down on stupid coding practices by greenhorns and enforce code maintainability.
They played us absolute fools.
int main()is the only function ever needed aside from loops, if you can’t implement what you need, then your project is of the devil.IF and GOTO are the only flow control we need; everything else is for cowards.
Goto is surprisingly readable.
Loops don’t get labels. Labels are awesome. Sprinkle in some goto so you can use labels.
In languages like python inside a loop you have
if condition: continue. Except continue means don’t continue, you skip to the next iteration without breaking the loop. That’s confusing as heck (and what iselsedoing on loops Guido???).if condition: goto loopis more honest.I also like that goto is “take my stack frame and run that procedure instead”, which is kind of unique and cool in its own way, and impossible to do with most lexical scoping systems. It’s reliable zero cost function calling (if you can make your optimizer happy).
Everyone loves repeating “goto considered harmful” and “numbering should start at zero”, but nobody critically thinks about those things. Rules are made to be broken.
~Oh, and the numbering argument is totally wrong… using one notation to advocate for another is silly. Offset from zero, but index by domain logic!~
Goto CAN be readable, it’s true.
The problem is that it’s easy to make code that is LESS readable; in order to prevent horrible unmaintainable spaghetti, it is forbidden nearly everywhere. A lot of coding ‘rules’ are really just ways to try to cut down on stupid coding practices by greenhorns and enforce code maintainability.
It’s a blessing and a curse. I’ll give you that.
spaghetti is delicious for a reason.