> I think that's a given. But I think what he was wanting to know is ...
> once you discover an infinite loop is running, what can you do to stop it
> other than restart the server?
>
> Which seems like a sound thing to want to know. It would be pretty
> obvious that if you don't discover an infinite loop while you're writing
> the routine, the next most likely time to discover it is when it runs.
> What then?
That's not such a simple question. How is the CF server supposed to
differentiate between a finite loop and an infinite loop? Is 1000
iterations too many? 10,000? 100,000? I'm sure there are valid processes
that could loop that many times and still have a definite exit point.
The only way for CF to tell what loops are infinite would be to examine the
loop logic and decide if the exit state would ever be met. Considering that
this could be incredibly difficult (or impossible) for even marginally
complex loops I don't see how this could be efficiently included in the CF
engine.
The best solution is to hire programmers that don't write infinite loops
<g>.
Regards,
Seth Petry-Johnson
Argo Enterprise and Associates
------------------------------------------------------------------------------
Archives: http://www.eGroups.com/list/cf-talk
To Unsubscribe visit
http://www.houseoffusion.com/index.cfm?sidebar=lists&body=lists/cf_talk or send a
message to [EMAIL PROTECTED] with 'unsubscribe' in the body.
