Path: utzoo!censor!geac!torsqnt!jarvis.csri.toronto.edu!rutgers!ucsd!hub!6600pete
From: 6600pete@ucsbuxa.ucsb.edu (GurgleKat [Pete Gontier])
Newsgroups: comp.sys.mac.programmer
Subject: Re: Wisdom of ExitToShell in a ShutDown proc
Message-ID: <4162@hub.UUCP>
Date: 4 Mar 90 17:31:02 GMT
References: <4143@hub.UUCP>
Sender: news@hub.UUCP
Reply-To: 6600pete@ucsbuxa.ucsb.edu
Lines: 17

From article <4143@hub.UUCP>, by 6600pete@ucsbuxa.ucsb.edu:
> In the process of debugging a ShutDown proc, I have told the debugger
> to 'es' (ExitToShell) a number of times. This has the curious but not
> surprising effect of restarting MultiFinder and all her default
> applications. Does anyone know if it would be a safe or wise practice
> to allow a user to ExitToShell from a ShutDown proc?

As I am told in mail, this has been hashed out on the net recently
(and I seem to in fact remember it vaguely...) and the answer was, finally,
no, it ain't wise to do this. The suggestion was to patch ShutDown. This
is why I vaguely remember the discussion. Someone said "Patch ShutDown?
When Apple's already provided ShutDown procs? Heresy!" And then someone
replied "Aw hell, go ahead and patch it. Apple already has."
--
Pete Gontier   | InterNet: 6600pete@ucsbuxa.ucsb.edu, BitNet: 6600pete@ucsbuxa
Editor, Macker | Online Macintosh Programming Journal; mail for subscription
Hire this kid  | Mac, DOS, C, Pascal, asm, excellent communication skills