Thread: alternative to cin

>When did I ever mention anything but the basic loop I made?<

Sorry I had no idea why you posted the asm. I assumed it was an attempt to justify your desicion not to turn on your compilers optimser. Which seemed like a likely shot in the dark considering you mentioned compiler optimisation.

>All that I was trying to show is that in unoptimized code, my use of the infamous goto would be more effecient.<

How does this show that? Have you even looked at the diassembly of the method I described that doesn't use the infamous goto. Efficiency is not an excuse for using goto in this case. Since you seem to be having a hard time -

while(1)
{
if(i>=0)break;
}

is the same as

while(i<0)
;

which compiles in a debug build to -

$L9393:
cmp DWORD PTR _i$[ebp], 0
jge SHORT $L9394
jmp SHORT $L9393
$L9394:

No compiler optimisation. No use of the infamous goto. 3 instructions.

I have to admit, in golfinguy's example, I don't see how the goto would be more efficient than the while loop. Both test to see whether to end the loop. Maybe I'm missing something.

Because a while loop has to test the value of its argument. Since one is always considered to be true, it continues on with what is inside the loop. However, my use of goto's eliminates the need to test the value of the argument.

P.S. Sorensen, I do use my compiler optimizer. I said that I know others that don't use it.

Also Sorensen, you did use an optimizer when you rewrote the loop. It was your brain, which is not a machine, but you still performed optimization.