Re: Writing error messages? Take II

Subject: Re: Writing error messages? Take II
From: iain -at- hairydog -dot- co -dot- uk (Iain Harrison)
To: techwr-l -at- lists -dot- raycomm -dot- com
Date: Thu, 2 Mar 2000 15:09 +0000 (GMT Standard Time)

> <<I don't think that I have ever seen that message [Abort, retry, fail]
> without a preceding line that tells me what has gone wrong. Something
> like:
> Drive a: not ready Abort, retry, fail?>>
> Sorry, I was imprecise. Without a _useful_ description of what has gone
> wrong. Why isn't the drive ready? Is it broken? Is it busy? Is it not
> responding for some unknown reason? Did it complete part of the task I
> asked
> it to do and the fail midway along?

The point here is that this is an OS message, not an application error
message, and the OS doesn't have that level of detail to pass on. The
request goes to the disk drive, and it responds "not ready". Giving more
information would be speculation.

An application programmer ought to capture these messages and add helpful
stuff, but that's not the OS' job.



iain -at- hairydog -dot- co -dot- uk
iainh -at- cix -dot- co -dot- uk

Previous by Author: Re: IP addresses/domain names at the end of a sentence
Next by Author: RE: Policy vs Procedure?
Previous by Thread: Writing error messages? Take II
Next by Thread: Word picture question

What this post helpful? Share it with friends and colleagues:

Sponsored Ads

Sponsored Ads