beely
12-10-2002, 08:30 AM
Originally posted by quzah
We aren't talking about self-modifying code here. Once compiled, your program is done. All checks are finished, unless it's a scriptible application, in which case, this whole point is moot anyway.
As such, there is no scenario I can envision where your example would be valid. Furthremore, why couldn't I just add another && sitution?
This isn't a holy war over the evils of continue. By all means, do whatever you want. Just make your code readable and clear so the next person that has to maintain your code knows what the hell is going on. That's the whole point.
In everything you code, make sure the next idiot that follows you knows what's going on. Code as if an idiot is going to have to read your code after you're done with it.
Quzah.
i agree to quzah's comment. however, using the bad structure could make the whole program more confusing. i try to avoid using "GOTO, continue, break" if necessary. all of the certain things that i mention is bad structure in my mind. if let say that if ppl wan to use with this statement, never mind. it's ok for that ppl, but if they use it in certain time, the whole program look like untidy, unstructure. This is not included on the flowchart.
&& shouldn't hardly disturb on the exe time. i just add a variable to control it. am i right ?
We aren't talking about self-modifying code here. Once compiled, your program is done. All checks are finished, unless it's a scriptible application, in which case, this whole point is moot anyway.
As such, there is no scenario I can envision where your example would be valid. Furthremore, why couldn't I just add another && sitution?
This isn't a holy war over the evils of continue. By all means, do whatever you want. Just make your code readable and clear so the next person that has to maintain your code knows what the hell is going on. That's the whole point.
In everything you code, make sure the next idiot that follows you knows what's going on. Code as if an idiot is going to have to read your code after you're done with it.
Quzah.
i agree to quzah's comment. however, using the bad structure could make the whole program more confusing. i try to avoid using "GOTO, continue, break" if necessary. all of the certain things that i mention is bad structure in my mind. if let say that if ppl wan to use with this statement, never mind. it's ok for that ppl, but if they use it in certain time, the whole program look like untidy, unstructure. This is not included on the flowchart.
&& shouldn't hardly disturb on the exe time. i just add a variable to control it. am i right ?