For loop horror
-
I just spent an hour trying to think why the process didn't work.
for(int nindex = MIN_VAL; nindex <= MAX_VAL; nindex++); { //50 lines of code that processes something }Maybe everyone has these kind of moments. :doh:Oh my god....and I was looking ....and looking....and looking.... The conditional statement was fine....and I couldn't find it at all....keep looking and reading all the comments here. Couldn't find it. I was about to give up and ask when BLAM!!!!! I saw it...there... That never happened to me. Luckily! I've done similar though and lost a good 3~4 hours of time trying to figure it out. I am actually surprised that this compiles though...and runs. Shouldn't the compiler complain about this?
Dewm Solo - Managed C++ Developer
-
I just spent an hour trying to think why the process didn't work.
for(int nindex = MIN_VAL; nindex <= MAX_VAL; nindex++); { //50 lines of code that processes something }Maybe everyone has these kind of moments. :doh:Dammit, I had to stick this in the IDE and debug it to work out what the hell was wrong with this. I think I've been doing a little too much ASP maintenance today :sigh:
-
if it makes you feel any better, it took me about 5 mins of looking at it over and over again before i noticed what you were talking about :doh:
~Nitron.
ññòòïðïðB A
startsame here
-
*beeeep* what's wrong...can't say "semicolon" ???
caridad
-
Oh my god....and I was looking ....and looking....and looking.... The conditional statement was fine....and I couldn't find it at all....keep looking and reading all the comments here. Couldn't find it. I was about to give up and ask when BLAM!!!!! I saw it...there... That never happened to me. Luckily! I've done similar though and lost a good 3~4 hours of time trying to figure it out. I am actually surprised that this compiles though...and runs. Shouldn't the compiler complain about this?
Dewm Solo - Managed C++ Developer
Dewm Solo wrote:
Shouldn't the compiler complain about this?
No, it's perfectly valid to stuff all of the loops processing into the
( ; ; )of aforstatement and create a loop with no explicitly defined code block. This has it's uses, but I always just enjoyed using it to obfuscate my code :) -
if it makes you feel any better, it took me about 5 mins of looking at it over and over again before i noticed what you were talking about :doh:
~Nitron.
ññòòïðïðB A
start -
A classic C/C++ error; you haven't been coding long enough if you haven't run into this one before.
Steve
-
if it makes you feel any better, it took me about 5 mins of looking at it over and over again before i noticed what you were talking about :doh:
~Nitron.
ññòòïðïðB A
startI didn't get it until Marc's comment about the body only running once.
This blanket smells like ham
-
Oh my god....and I was looking ....and looking....and looking.... The conditional statement was fine....and I couldn't find it at all....keep looking and reading all the comments here. Couldn't find it. I was about to give up and ask when BLAM!!!!! I saw it...there... That never happened to me. Luckily! I've done similar though and lost a good 3~4 hours of time trying to figure it out. I am actually surprised that this compiles though...and runs. Shouldn't the compiler complain about this?
Dewm Solo - Managed C++ Developer
Dewm Solo wrote:
I am actually surprised that this compiles though...and runs. Shouldn't the compiler complain about this?
Yeah. While it should of course compile, I'd want this warning: http://msdn2.microsoft.com/en-us/library/9x19t380(vs.80).aspx[^]
[My Blog]
"Visual studio desperately needs some performance improvements. It is sometimes almost as slow as eclipse." - Rüdiger Klaehn
"Real men use mspaint for writing code and notepad for designing graphics." - Anna-Jayne Metcalfe -
if it makes you feel any better, it took me about 5 mins of looking at it over and over again before i noticed what you were talking about :doh:
~Nitron.
ññòòïðïðB A
startI had to look for help :)
xacc.ide
The rule of three: "The first time you notice something that might repeat, don't generalize it. The second time the situation occurs, develop in a similar fashion -- possibly even copy/paste -- but don't generalize yet. On the third time, look to generalize the approach." -
Dewm Solo wrote:
I am actually surprised that this compiles though...and runs. Shouldn't the compiler complain about this?
Yeah. While it should of course compile, I'd want this warning: http://msdn2.microsoft.com/en-us/library/9x19t380(vs.80).aspx[^]
[My Blog]
"Visual studio desperately needs some performance improvements. It is sometimes almost as slow as eclipse." - Rüdiger Klaehn
"Real men use mspaint for writing code and notepad for designing graphics." - Anna-Jayne Metcalfe -
I just spent an hour trying to think why the process didn't work.
for(int nindex = MIN_VAL; nindex <= MAX_VAL; nindex++); { //50 lines of code that processes something }Maybe everyone has these kind of moments. :doh:I was starting to get mad at this code, thinking it is one of those "inside" jokes where everybody laughs until you start laughing, then they laugh harder cause there is no joke. Nobody said what the problem was. Then after reading all the comments, I went back and reviewed it again. I found the issue! Funny how it never shows up till the end. Hogan
-
I was starting to get mad at this code, thinking it is one of those "inside" jokes where everybody laughs until you start laughing, then they laugh harder cause there is no joke. Nobody said what the problem was. Then after reading all the comments, I went back and reviewed it again. I found the issue! Funny how it never shows up till the end. Hogan
-
I just spent an hour trying to think why the process didn't work.
for(int nindex = MIN_VAL; nindex <= MAX_VAL; nindex++); { //50 lines of code that processes something }Maybe everyone has these kind of moments. :doh:When happened to me, I thought for a (long) while about a compiler bug, before finding the ****** semicolon. :)
If the Lord God Almighty had consulted me before embarking upon the Creation, I would have recommended something simpler. -- Alfonso the Wise, 13th Century King of Castile.
-
When happened to me, I thought for a (long) while about a compiler bug, before finding the ****** semicolon. :)
If the Lord God Almighty had consulted me before embarking upon the Creation, I would have recommended something simpler. -- Alfonso the Wise, 13th Century King of Castile.
took me about five seconds to see the error. maybe I've stumbled into most shit already.
Larswad