FOR loops are confusing

yes

The Truth

We Have To Go Deeper!

The End?

The End.

i don't know how FOR loops work

O, MASTER OF R3C0RD1NG i thought it was seconds faster

FOR loops aren't confusing if you make a small amount of effort to understand them. FOR loops take a variable, reset it to value 1, then take it to value 2, adding whatever the STEP is set to each time. (by default, it just adds one until it reaches value 2)

FOR (variable)=(value 1) TO (value 2) STEP (step)
 PRINT "Hi! ";(variable)
NEXT

FOR I=0 TO 3 STEP 2
 PRINT "Hi! ";I
NEXT

enter that code and see what happens. try changing one thing. try removing the STEP.

well, if you dont know how a for loop works then why are you even saying they are worse.. its like saying im the best person in the universe without even looking at anyone else or like saying "Bob the builder gAmE iS tHe BeeSt iN thE UniVeRSe and minecraft is so dumb because it has nothing to do" without ever playing minecraft, its just not good, or like disliking someone for no reason without knowing anything about them. label loops can be good in certain situations but honestly if your need it just use another loop or a DEF. also a for loop is not something you would use as a game loop, unless you totally screwed things up they are used for other things. now while wend loops are my fav, but i also use repeat until ones too. use them. use defs. learn them then once you have, come back here and see all your mistakes, or just sty with label loops and never make a good game and have problems for the rest of your hopefully short coding life.

now heres the problem, imagine yourself trying to catch a penny in mid air, but because you are using a label loop it goes too fast and skips the line that catches it making you never able to get it. speed does not always mean "better", also anyone who has used label loops for long enough knows they cause lots of glitches and problems in your programs that are hard to fix, now when i switched to while/wend loops literally all my glitches went away in my program and it was a GREAT thing too. very worth the time to switch your code over. anyways why am i here..? idk, bye.

i ^gr^^. i used to have a heck ton of problems with goto@loops but they mostly went away except me forgetting to define a variable.

fun fact you NEED to use for loops to load a map on screen, at least of what i know, ex:

FOR I=0 TO 3
BGSCREEN I,127,128'(or I,64,64)
NEXT
/the rest of map loading code

FOR I=0 TO 3
BGSCREEN I,127,128'(or I,64,64)
NEXT
/the rest of map loading code

edit button too small on the end of the code its

'the rest of map loading code

FOR I=0 TO 3
BGSCREEN I,127,128'(or I,64,64)
NEXT
/the rest of map loading code

actually that only if you want to make it faster and easyer, you can do without it would just be a lot more code. but yes good

well...if having a loop that is a few milliseconds slower than a GOTO loop doesn't bother you then use the more advanced loops if you want you game to run AS FAST AS POSSIBLE (like if your making a game about going fast!) use GOTO loops. [EDIT:added ICODE, this message and a dot]

I don’t think a few milliseconds will affect gameplay very much at all. I find it hard to believe that your only argument to support your enthusiasm for Label loops is something that you didn’t even know until you saw someone say it a few days ago.

Quote from MASTERR3C0RD: "GOTO loops aren't that much more faster. We're talking milliseconds here, which doesn't matter unless you're making a very very advanced game where those milliseconds are the difference between staying above 30FPS or dropping frames like it's hot. So stop being an annoying pest and shut up about things you know nothing about". the key part is:"GOTO loops aren't that much more faster. We're talking milliseconds here, which doesn't matter unless you're making a very very advanced game where those milliseconds are the difference between staying above 30FPS or dropping frames like it's hot." well, more specifically, the "which doesn't matter unless you're making a very very advanced game where those milliseconds are the difference between staying above 30FPS or dropping frames like it's hot."

i have a joke idea:edit the for to be CAPITAL and make it use ICODE! it'd be a joke about FOR loops.

i have a joke idea: how about you stop commenting every two seconds like this is miiverse or something? it'd be a joke about your inability to read any mood.

i have a joke idea:how about you stop thinking i don't know the difference between SBS and Miiverse it'd be a joke about how dumb you are and how smart i am

I like how instead of having a point, you now just insult people for no good reason.

FOR I=0 TO 3
BGSCREEN I,127,128'(or I,64,64)
NEXT
/the rest of map loading code

GOTO can emulate any other loop structure. They exist for convenience, as do the named commands and BASIC itself. Programming as we know it is about abstraction. Anyway, for comparison:

FOR I=0 TO 3
 BGSCREEN I,127,128
NEXT

can be accomplished with this literal jump:

VAR I = 0
@LOOP_1
BGSCREEN I,127,128
DEC I, -1 'for "speed"
IF I <= 3 THEN GOTO @LOOP_1

In addition, a finite loop can be "unwrapped" by writing out every instruction.

BGSCREEN 0,127,128
BGSCREEN 1,127,128
BGSCREEN 2,127,128
BGSCREEN 3,127,128

The counting "FOR" loop allows us to not worry about iterator variables, it handles the increment itself. Most of the "debate" occurring in the comments here seems to be DSM not bothering to learn structures like this. I'm sure he'll choose the unwrapped version when checking all 512 sprites--after all, it's faster that way.

FOR I=0 TO 3
BGSCREEN I,127,128'(or I,64,64)
NEXT
/the rest of map loading code

DaSonicMario, if you want the most speed for your programs, don't use Python, Lua, or C#! Use Assembly! It's so much faster! Sure you sacrifice a little code readability, but in the end, it's worth it.