Another problem!!

[Sidoh]

If you're infinitely looping you're bound to access some restricted memory sooner or later.

Not if you're continuously re-examining the same memory!

Code: [Select]

while(true);
I doubt the above presents much threat of accessing dangerous memory.

[Warrior]

If you're infinitely looping you're bound to access some restricted memory sooner or later.

Not if you're continuously re-examining the same memory!

Code: [Select]

while(true);
I doubt the above presents much threat of accessing dangerous memory.

That's true but how often is it that you do an infinite loop withought having any code in the middle? You're going to currupt the stack sooner or later.

[Sidoh]

That's true but how often is it that you do an infinite loop withought having any code in the middle? You're going to currupt the stack sooner or later.

That's still a terrible generalization...

[Warrior]

Yea I guess, I assumed he knew what I meant.

[iago]

That's true but how often is it that you do an infinite loop withought having any code in the middle? You're going to currupt the stack sooner or later.

Take a look at all the programs in this folder -- they're programs for my microcontroller.  Notice what they all have in common?  They all take place in an infinite loop.  And none of them corrupt the memory. 

Generally, they're a finite-state-machine, waiting for events, but there's no way to sleep on that uC, since my code is the only code running (no library, no kernel, etc). 

[Warrior]

Cool.

[MyndFyre]

That's true but how often is it that you do an infinite loop withought having any code in the middle? You're going to currupt the stack sooner or later.

Code: [Select]

while (true)
{
i++;
j++;
k++;
l++;
m++;
n++;
o++;
}
No stack corruption.

[Warrior]

Ugh screw you guys :/

[Sidoh]

Ugh screw you guys :/

Because you're wrong?

[Warrior]

http://en.wikipedia.org/wiki/Stack_overflow

"The most common cause of stack overflows is infinite recursion."

http://en.wikipedia.org/wiki/Infinite_recursion

[MyndFyre]

http://en.wikipedia.org/wiki/Stack_overflow

"The most common cause of stack overflows is infinite recursion."

http://en.wikipedia.org/wiki/Infinite_recursion

Okay, first of all, stack overflows != stack corruption.  Second of all, infinite looping != infinite recursion.

Infinite looping:

Code: [Select]

while (true) ;
Infinite recursion:

Code: [Select]

void doStuff(int a)
{
 doStuff(++a);
}
Jackass.

[iago]

http://en.wikipedia.org/wiki/Stack_overflow

"The most common cause of stack overflows is infinite recursion."

http://en.wikipedia.org/wiki/Infinite_recursion

Okay, first of all, stack overflows != stack corruption.  Second of all, infinite looping != infinite recursion.

Infinite looping:

Code: [Select]

while (true) ;
Infinite recursion:

Code: [Select]

void doStuff(int a)
{
 doStuff(++a);
}
Jackass.

Exactly! 

[Warrior]

Second of all, infinite looping != infinite recursion.

Infinite recursion, a special case of an infinite loop, is an infinite loop caused by recursion.

[Sidoh]

Second of all, infinite looping != infinite recursion.

Infinite recursion, a special case of an infinite loop, is an infinite loop caused by recursion.

And Rolle's Theorem is a special case of the Mean Value Theorem.  That doesn't make them the same thing.  Just because two things are related doesn't mean they're completely synonymous.

[Warrior]

Second of all, infinite looping != infinite recursion.

Infinite recursion, a special case of an infinite loop, is an infinite loop caused by recursion.

And Rolle's Theorem is a special case of the Mean Value Theorem.  That doesn't make them the same thing.  Just because two things are related doesn't mean they're completely synonymous.

And? They're still related so I can call infinite recursion and infinite loop if I damn well feel like it and I will still be right.

Which makes me right.