when is the last time you use "if"? thats a forward jump... when is the last time you use "while" and "for"? thats the backward jump. except the language has made them a little bit organized for you
No that is called a "conditional loop", if you were serious I would advise you to pick up your books again ![Smiley :)](https://www.eevblog.com/forum/Smileys/default/xsmiley.gif.pagespeed.ic.R8GFI-pF6f.png)
What do you think a backwards jump is used for, 99.99% of the time? Mechatrommer obviously does not need to be corrected.
![Smiley :)](https://www.eevblog.com/forum/Smileys/default/xsmiley.gif.pagespeed.ic.R8GFI-pF6f.png)
You do not need a book to know how to use a conditional loop or a backwards jump, and picking up a book to read the name is not going to teach you how to code.
![Smiley :)](https://www.eevblog.com/forum/Smileys/default/xsmiley.gif.pagespeed.ic.R8GFI-pF6f.png)
I think you're joking, because of the smiley, but it is hard to tell.
![Smiley :)](https://www.eevblog.com/forum/Smileys/default/xsmiley.gif.pagespeed.ic.R8GFI-pF6f.png)
![Smiley :)](https://www.eevblog.com/forum/Smileys/default/xsmiley.gif.pagespeed.ic.R8GFI-pF6f.png)
**To make any kind of loop, the PC is jumping back in the machine code. If you want the code to execute only top to bottom, you have to redundantly add the same code over and over until you run out of space. lol.
In general, it is better to write code in such a structure that you CAN ignore some of the details and not get into trouble. But if you remove yourself so far from what is actually happening, you can end up in a situation where you CANNOT write code without following specific structure, because you have no clue what is actually happening. This might be the "best" way to write code for certain complicated project, but there are some things which you will not be able to do effectively/practically due to loss of efficiency and not enough speed and memory in the world to compensate. One should maybe try to remember how to ignore the rules without breaking the code, even if one rarely has to do it. And be conscientious to tidy up these potential sources of error where it does not matter one way or the other, even if you ARE 100% aware of how to write efficient and clear "bad/spaghetti" code, esp because one day you might have to support your own code and on this day you might not be as smart. I treat future me as pretty dumb. If you have a section of code with one entry, one exit, and documented with memory/stack usage, it has this advantage: no matter how complicated it is, even if you can't figure out how it works to save your life, because whoever wrote it (including past you) is smarter (or just has totally alien thought process and code style) than (present) you, you can more easily remove and rewrite the entire section without fucking up something else.