Scares zoomers shitless

>Scares zoomers shitless

Attached: file.png (300x201, 14.62K)

We tried unstructured programming before. It didn't end well.

I use goto sometimes. When it is the cleanest solution.

stop doing it jiji, we all know goto is shit
t. jiji

Yeah having control flow that jumps significant parts of the code defiantly scares people, but its not just zoomers.
>harder to maintain
>harder to debug
>harder to understand at a glance what is happening
>prone to knowledge silos

goto is absolute cancer and should be avoided at all costs

Do you also want to leave out the saw when working with wood?

longjmp to random memory address

>Scares boomers shitless

Attached: file.png (275x44, 16.33K)

deranged webdevs, gotos are used only sporadically, and there usually is a good reason for it
there won't be more than 3 in any particular piece of code you will examine

>We tried unstructured programming before. It didn't end well.

Programming would not be programming if it weren't structured. Your inability to CTRL+F to find the label within the code is your own limitation.

>Yeah having control flow that jumps significant parts of the code defiantly scares people, but its not just zoomers.

It only scares 55 IQ midwits who don't actually program, but rather do what their corporate overlord tells them to do (and how to do it).

>harder to understand at a glance what is happening
Sure dude, because labels are within the same block of code and there can only be one label: per block... but in your delusional world OOP is easier to figure out at a glance with many functions and code blocks hidden away in some class somewhere.

>goto is absolute cancer and should be avoided at all costs
It's an excellent way to break nested loops or skip code that would otherwise require conditional checks. I'm sure in your mind a chain of "if-else-elseif" would be 'smarter' than a single "if done goto here".

It's amazing how stupid people are today. Decades of drinking fluoridated water and beverages has truly cause IQ deficiencies.

Things I will happily take goto over include:
>copy-pasting cleanup code at each possible exit from a function
>routing all allocations through the boehm-demers-weiser garbage collectore
>using GCC extensions to approximate defer
>using C++ fuckery to approximate defer
>using C++ exceptions
>using any C++ feature, as we will be switching to C++ shortly after the sun fucking explodes
>reimplementing exceptions in C using setjmp/longjmp
>reimplementing exceptions in C by manually unwinding the stack
>writing an entire programming language that occupies juuust the right spot in abstraction/complexity/portability/performance space needed to solve the Final Problem of C

goto is just a poor man's call/cc

>getting filtered by a fucking JMP instruction
zoomers really are the the most pathetic generation

Your goto is pointing to the wrong label.

There's a reason we don't write assembly for everything, you know.

>NOOOO YOUR C LANGUAGE IS NOT LOW LEVEL BECAUSE OF HOW OUT OF ORDER MODERN X86 IS
>NOOOO YOU CANT USE GOTO YOURE SUPPOSE TO CODE LOGICALLY AND SEQUENTIALLY
Christ make up your mind

>reimplementing exceptions in C using setjmp/longjmp
sounds interesting, how do i do it :>

use setjmp instead of try/catch
use longjmp instead of throw
pretty straightforward

I agree. If statements are cancer and using any label other than start: is bloat.

ok, that was boring. now im uninterested -_-