>goto is harmful!
Goto is harmful!
Carson Powell
Other urls found in this thread:
tumblr.com
koblents.com
twitter.com
Liam Ortiz
Oliver Morgan
I love goto so much
fortran is my favourite language
Bentley Rogers
OP:
if(OP) goto faggot;
faggot:
printf("OP is a fag"); goto OP;
Daniel Butler
Considering goto harmful is so 1999. I'm pretty sure at this point we have moved on to considering all imperative programming constructs harmful.
Lincoln Sullivan
OO is much more harmful. You can actually see the code structure and flow when you use goto while OO is a fucking massive "code designer flowchart" mess that is near-impossible to debug and fix.
Jason Peterson
goto is so good and delicious my friend. I don't bother writing functions anymore, I just write what I call goto functions. e.g
int main(void) {
int n = 2;
goto double; // double n
return_double:
printf("%d\n", n);
return 0;
double:
n = n
Jack Stewart
>You can actually see the code structure and flow when you use goto
No, you can't. That's why it's called spaghetti code you imbecile.
Andrew Bennett
Anything can be harmful if done incorrectly. Goto just happens to be easier to fuck up
Jacob Nelson
>the absolute state of programming
imagine being part of an industry that has to tailor-make languages just so pajeet doesn't fuck it up.