At 05:49 PM 12/27/98 -0500, Chris Nandor wrote: [locking code snipped] > >I think that should lock the file, and then unlock it open exiting the >program, even if it exits prematurely (unless MacPerl itself dies). > >Any thoughts? Well, David's testing looks good, so that's a good start. I was wondering, though, about the case in which MacPerl dies. Now, Netscape has packaged something or other with Communicator 4.5 that runs when Communicator dies to ask you to file a crash report with Netscape. Annoying, yes, considering that Communicator still crashes relatively often, but if it were possible to do the same thing with a MacPerl program -- to enable something to run on a crash and, better yet, to be able to pass data or (even better) code to be exec'd (or something like that) to it to clean up after a horrible disaster -- then that would get around the problem of MacPerl dying quite nicely in most cases. Would that work and be feasible, or am I just being fanciful here? Not sure at all of how Netscape's crash detection works, Eric --------------------------------------------- Eric Albert ejalbert@cs.stanford.edu http://www.stanford.edu/~ejalbert/ ***** Want to unsubscribe from this list? ***** Send mail with body "unsubscribe" to mac-perl-request@iis.ee.ethz.ch