At only one point there was a hint that something was wrong
In fact it will waste no time at all, the compiler sees that there is nothing in the loop and so removes it from your code
This was interpreted by ME to mean, if the function is not in the
void loop()
{
forward();
}
It is ignored.
Not
int i;
for(i=0;i<2000;i++);
Is removed from the function
void forward()
{
PORTB = 1 << PORTB;
int i;
for(i=0;i<2000;i++);
}
At the point when i stated
You can waste some cycles before a function, during or after a function.
Why did someone not ask "How do you waste cycles in a function?"
Here are the following assumptions i make or have made.
Those of us learning, assume the more professional programmers can see errors within our code before we can.
It is assumed socially, that if a person is going to or is making an err, to let them know.
Professionals in almost any area of expertise, except Psychology, make the assumptions that , beginners in their field are like minded.
Professionals (Professors) in a field are like minded.
Assuming that all people think alike, is the one assumption all professionals make were noted, therefore any advancement in any industry is thawted by these assumptions.
P.S. I miss the, someone has just replied to your topic, warning!