🚀 go-pugleaf

+>run it. Does anybody have an ideas or suggestions to remedy this
+>problem?
+>
+
+By far the most common cause of this particular problem is saving
+you code out to a fast load and save format file after heavy editing.
+This can sometimes cause slight corruption in the threaded p-code which
+is saved.  You can cure this by loading the program, going to the
+"Save As" menu item of the file menu, and making sure that "Save file
+as text (readable by other programs)" option is selected.
+
+By the way, I highly recommend *never* saving in fast load/save format
+for the simple reason that if even one bit is changed from what it should
+be (from whatever cause), the entire file is a complete loss.  However,
+You stand a very good chance of recovering most, if not all, of a file
+if it is saved in Text format.

Does this continue to hold true for those who conscientiously save as we edit 
so there is a minimal change with each save?

Keith.
-- 
D.K.Higgs  DATA+@osu.edu  a.k.a  dhiggs@magnus.acs.ohio-state.edu _____   __o
Ohio State University Libraries, Acquisitions Department      -------    -\<,
Continuation Acquisition Division                              ------ ( )/ ( )
~~(614)292-6314~~~~~~fax(614)292-2015~~~~~~~~~~\_________/~~~~~~~~~~~~~~~~~~~