Path: utzoo!utgpu!watmath!maytag!watstat!dmurdoch
From: dmurdoch@watstat.waterloo.edu (Duncan Murdoch)
Newsgroups: comp.lang.pascal
Subject: Re: TP5 losing work
Keywords: TP5, lost source files
Message-ID: <273@maytag.waterloo.edu>
Date: 25 Jun 89 01:05:54 GMT
References: <2472@blake.acs.washington.edu> <1496@bucket.UUCP>
Sender: daemon@maytag.waterloo.edu
Reply-To: dmurdoch@watstat.waterloo.edu (Duncan Murdoch)
Distribution: na
Organization: U. of Waterloo, Ontario
Lines: 14

In article <1496@bucket.UUCP> leonard@bucket.UUCP (Leonard Erickson) writes:
>Yes. TP keeps the source in RAM. All changes exist only in RAM until
>you *explicitly* save the file. My advice is to hit the F2 key (save
>file) and *then* recompile/execute. 

There's also a compiler option that automatically saves
changes every time before you run something.  It costs a little bit of time
on each run, but saves a lot on each crash.

It's in the Environment Menu of TINST, under Edit Auto Save, and defaults to
Off, presumably to make the compiler look good in benchmarks, rather than in
real life.

Duncan Murdoch