force quit question

[Jim McNeely]

Here is a (probably embarrassing) newbie question for you.

Suppose you put some ill-advised code in a file that results in an  
endless loop, and you have to force quit revolution. If you go back  
to that file and resume work, should you suppose that it is damaged,  
or should you assume that all is well except unsaved changes were lost?

In other words, what is the conventional wisdom in this circumstance,  
besides avoiding putting dumb endless looping code into your app?

Thanks,

Jim McNeely