[Info-vax] Unexpected error using ZIP for OpenVMS

[Steven Schweda]

> In the "expected" case, something that is assumed to be there, and
> needs to be there, wasn't. So you were expecting this?

   Huh?  In the "expected" case, the program complains about
an error made by the user.  In my case, providing an invalid
input file specification.  In the "unexpected" case, the
program can't read a perfectly good file, apparently because
of a problem in the program (or a shortcoming in the C
run-time I/O system).  I expect the program to complain when
the user makes a mistake like that.  I don't expect it to
complain about being unable to read a valid input file.

> > [...]  Time spent on specious nit-picking might be
> > better spent on testing the actual code involved here.

> I don't have the code, and don't have the time. (Yeah, I have the time
> to write this, but debugging would certainly take longer, as I'd have
> to get the code, read the code, try the code, etc. So please spare
> me!)

   Read it again?  I didn't ask you to diagnose or fix the
problem.  I believe that I've done those things.  What might
be useful is to have others (even you) test the fix to verify
that it works, and doesn't wreck anything which worked before
the (so-called) fix was applied.  So, "try the code" is what,
I claim, would have some actual value.  (More, that is, than
rambling on about the meaning of "unexpected" in this
context.)

   On the bright side, this change will probably appear in a
(relatively harmless) beta kit before Zip 3.1 is released, so
there's some chance that any new or remaining problems will
be detected before severe damage is done, but the sooner any
problems are found, the happier I'll be, and before the next
beta release would be better than after.