force quit question

[J. Landman Gay]

Jim McNeely wrote:
> 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?

Rev stacks are entirely RAM-based when they run, so any damage to the 
actual file on disk is very, very rare. You can assume that any unsaved 
work will be lost, but otherwise you should be fine. The only thing lost 
is the current contents of RAM.

-- 
Jacqueline Landman Gay         |     jacque at hyperactivesw.com
HyperActive Software           |     http://www.hyperactivesw.com