Mail Archives: djgpp-workers/1996/10/06/13:42:15
> 1) The messages that indicate problems (like when $DJGPP is not
> found) should attract attention in both the text printed to the screen and
> the report file. Make them stand out (with asterisks, exclams, preceeded
> by ``ERROR:'' or with anything else), and print them surrounded by blank
> lines). Right now they are lost among the voluminous output, most of
> which is just saying the gory details. (I unset $DJGPP to see what
> happens and at first thought that the program didn't detect this, since no
> error message caught the eye.)
I wonder if it would be possible, that ONLY if there are no errors do
any warning or info lines get printed? That way, if there are errors,
you'll see nothing but errors.
> 3) When no problems were detected, I suggest telling this as the
> last line of the report, both to the screen and to the file. And make
> this line stand out also.
Also, if the system is OK, then and only then suggest that they put
djverify in autoexec.bat with a "quiet" switch.
> 5) Why a separate batch file? I think DJVERIFY itself should be
> a batch file, so users won't need to remember 2 names.
To see if djgpp programs can run at all - the stub errors, remember?
- Raw text -