caglar said:
I feel more comfortable with:
#define TRUE 1
do{
//...
}while(TRUE);
and I think that this is semantically more sound than the for(;
for
me. Because when i see this snippet, in the code
the compiler in my head automatically translates it to: "do the stuffs
in the loop while all conditions are satisfied".
As I'm sure you know, it's semantically identical.
Also, putting the condition at the bottom makes it less obvious
that it's an infinite loop. And both "while (1)" and "for (;
"
have the considerable advantage of being common C idioms.
I rarely see or use do-while loops in C. (I think the last time I
used one was in my IOCCC entry; I formatted the code so the "while"
looked, at first glance, like it was the top of a while loop rather
than the bottom of a do-while loop.)
Also some weird staff(not sure if this is previously mentioned before)
like the following is possible which i'd recommend you to avoid from:
#include <stdio.h>
#include <stdlib.h>
int main(){
int test_var = 0;
loop:
test_var++;
if( test_var == 100 ) {
goto break_loop;
}else {
printf( "I'm inside the loop: %d", test_var );
}
goto loop;
break_loop:
printf("I'm out of loop\n");
return EXIT_SUCCESS;
}
Yeah, and you can also use a global array as a call stack, so you
can put all your code in main() and use gotos instead of function
calls and returns. (Each return would have to be a switch statement
so it jumps to the correct label, though you can use a simple goto
if the "function" is "called" from only one place.) And you can
put a label on each statement:
L10: printf("This is a loop\n");
L20: goto L10;
And if that's not painful enough, you can glue small sharp pins to the
keys on your keyboard and soak your feet in a bucket of ice water.
