Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Posting-Version: version B 2.10.2 9/5/84; site tmq.UUCP
Path: utzoo!watmath!clyde!burl!ulysses!mhuxr!mhuxt!houxm!ihnp4!tmq!darin
From: darin@tmq.UUCP (Darin Adler)
Newsgroups: net.micro.mac
Subject: Resume
Message-ID: <189@tmq.UUCP>
Date: Sun, 12-May-85 18:32:03 EDT
Article-I.D.: tmq.189
Posted: Sun May 12 18:32:03 1985
Date-Received: Tue, 14-May-85 20:14:21 EDT
References: <6689@ucbvax.UUCP> <26700013@inmet.UUCP>
Organization: tmq/ICOM Buffalo Grove, IL
Lines: 17

> 
> Writing a resume procedure is no mean feat.  Since exit to finder
> doesn't rebuild the system heap from scratch your takings some risks in
> letting the finder attack on your disks at that point.  Consider what
> happens if it rewrites a disk's directory without checking that the
> directory is absolutly pure and noble, bye bye data ...
> ... My only use of this feature is to get some oportunity to look at
> things prior to the machine rebooting.

I have used resume procedures that allow a "Save and Quit" or "Quit" option
(similar to the ones in MacWrite).  It is true that the system heap may be
mangled ... maybe a warning to the user is in order.  I have not had trouble
using a resume procedure - I have resumed many time without noticing ill
effects, so I think that destruction of the system heap is fairly rare.

Darin Adler
ihnp4!tmq!darin