Kinetic Code Camp - Bring your skills, or lack thereof.. :dumpster_fire:

[klincecum (Kevin Lincecum)]

Snippet: Dumb, but occasionally useful things to do with a for loop…

Main Post → Here!

@klincecum

Those of you a little more advanced readers may be seeing how I described the above rules, and either know or suspect that that is not the end of the story, and indeed

it is not, which I will cover in a snippet, as it is a more advanced topic…

The rules & structure…

@klincecum

The FOR loop is composed of the following structure:

for( [ init statement ] ; [ condition statement(evaluates to boolean) ] ; [ iteration statement ])
{
[ This is the code block ]
Code you want to run until your condition is false goes here…
}

• init statement: This statement runs once before the loop
• conditon statement: This statement needs to evaluate to a boolean (true/false). While this statement is true, your loop will continue to run. (Unless you exit manually, or error…)
• iteration statement: This statement will run every iteration of the loop, after the code in the code block.

---

Which means that the below dumb code is perfectly valid:

for(Console.WriteLine("Hello"); true; Console.WriteLine("World!"))
{
    Console.WriteLine("Is this thing broken?");
}

Output, which repeats forever:

Hello                          <-- Init statement
Is this thing broken?          <-- Code Block
World!                         <-- Iteration statement
Is this thing broken?
World!
Is this thing broken?
World!
Is this thing broken?
World!

So, you can do some crazy stuff with for? As you can imagine, yes, yes you can.
Should you? Mmmm, most times probably not, but I imagine the more experienced of you can see how this can be used for good.

I would advise if you use “for” outside of the traditional way, to make it crystal clear in your code what you are doing, or you may confuse someone easily, including yourself!