[Info-vax] Unexpected error using ZIP for OpenVMS

AEF spamsink2001 at yahoo.com
Fri Dec 23 21:29:00 EST 2011


On Dec 22, 8:10 am, Paul Sture <p... at sture.ch> wrote:
> On Wed, 21 Dec 2011 18:28:55 -0800, AEF wrote:
> > On Dec 20, 11:56 pm, Steven Schweda <sms.antin... at gmail.com> wrote:
>
> >>    Huh?  Why would the user expect that he was making a
> >> typing error, or that his file was corrupted?
>
> > Well, I didn't think of that possibility. Yeah, I don't suppose a user
> > would not expect to make a typing mistake at a particular time, but you
> > do have to assume you'd make typing mistakes _some_ of the time.
>
> From the programming point of view, any invalid user input is an
> *expected error* (and nowadays with web attacks must be assumed to be
> potentially malicious).
>
> An *unexpected error* from the programming point of view is usually
> caused by a hardware fault or human error (disk getting full). And as
> Philip Helbig pointed out with his "Shouldn't get here" example, it can
> be a programming logic error.

OK, so users errors are expected, but hardware errors and programmer
errors aren't.

OK, so if you don't expect hardware errors, why are there monitoring
programs for such things? Are these monitoring programs also
unexpected? Don't hardware errors produce error messages? Were the
people who wrote these error messages not expecting them? If not, why
did they write them?

OK, so if you don't expect programming errors (What?!), why are bug
fixes? Are bug fixes unexpected, too? Are debuggers also unexpected?

> --
> Paul Sture

AEF



More information about the Info-vax mailing list