Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!mnetor!uunet!husc6!endor!singer
From: singer@endor.harvard.edu (Richard Siegel)
Newsgroups: comp.sys.mac
Subject: Re: Multifinder bugs
Message-ID: <3026@husc6.UUCP>
Date: Wed, 21-Oct-87 09:16:07 EDT
Article-I.D.: husc6.3026
Posted: Wed Oct 21 09:16:07 1987
Date-Received: Fri, 23-Oct-87 06:24:50 EDT
References: <11877@decwrl.DEC.COM> <1331@bgsuvax.UUCP>
Sender: news@husc6.UUCP
Reply-To: singer@endor.UUCP (Richard Siegel)
Organization: THINK Technologies, Inc., Bedford, MA
Lines: 32

In article <1331@bgsuvax.UUCP> denbeste@bgsuvax.UUCP (William C. DenBesten) writes:
>In my opinion, the 'bug' is with the system error handler, or the
>application's error handler.  It should report some meaningful

	The System Error handler isn't responsible for handling file-system
or resource manager errors, and to expect it to do so is asking a little
much; generally it should be up to the application to respond to a file
system error, post a meaningful message, and handle it appropriately.

	The System Error handler itself cuts in when a truly fatal
error has occurred; odd address, out of memory, and illegal instruction
are typical errors to see. In this case, the system is extremely unstable,
and the System Error handler needs to be able to do its thing using
a bare minimum of system resources.

>Unfortunately, the text for all these messages would take up
>incredible amounts of room.

	This is true.



		--Rich



**The opinions stated herein are my own opinions and do not necessarily
represent the policies or opinions of my employer (THINK Technologies, Inc).

* Richard M. Siegel | {decvax, ucbvax, sun}!harvard!endor!singer    *
* Customer Support  | singer@endor.harvard.edu			    *
* THINK Technologies, Inc.  (No snappy quote)                       *