delorie.com/archives/browse.cgi   search  
Mail Archives: djgpp-workers/1996/10/06/14:24:47

Message-ID: <325823E1.3B89@cs.com>
Date: Sun, 06 Oct 1996 14:25:53 -0700
From: "John M. Aldrich" <fighteer AT cs DOT com>
Reply-To: fighteer AT cs DOT com
Organization: Three pounds of chaos and a pinch of salt
MIME-Version: 1.0
To: DJ Delorie <dj AT delorie DOT com>
CC: eliz AT is DOT elta DOT co DOT il, djgpp-workers AT delorie DOT com
Subject: Re: DJVERIFY 0.1a uploaded
References: <199610061740 DOT NAA06033 AT delorie DOT com>

DJ Delorie wrote:
> 
> 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.

This is basically the way I intend the final program to run:

1) In quick mode, it will behave as you describe, DJ - only displaying
messages if errors are found.

2) In summary mode, it will list each item it examines along with a
report on whether it checks out, or if not, what is wrong.  Errors will
be highlighted by boldfacing the text (and using asterisks in the report
file).

3) In interactive mode, it will display a menu listing each item in a
table, with the items on the left and a "PASS" or "FAIL" message on the
right, with "FAIL" highlighted.  The user can then select the indicated
items for a detailed report and suggestions on correcting the problem.

> Also, if the system is OK, then and only then suggest that they put
> djverify in autoexec.bat with a "quiet" switch.

Good idea.

> >       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?

See my reply to Eli for the reasons why I did this.  The other reason I
created a separate batch file is so that it can be used (theoretically)
to debug other programs besides DJVERIFY by using the '-F' switch.  If
the error code functionality is not going to be put into the standard
stub, then this point is moot, but it's worth considering IMHO.

BTW, can I use the conio textcolor functions in conjuction with the
stdio display functions?  I want to be able to set text attributes
without having to depend on having ANSI.SYS loaded, but I also am unable
to find a conio equivalent of vprintf(), which is needed by the output
functions to split messages between the screen and the report file. 
(This is how I implemented a print echo library for my C classes in
school.)  If I do need the conio functions to get the text attributes,
would it be possible for somebody to contribute a 'vcprintf()'
function?  Thanks!

-- 
---------------------------------------------------------------------
| John M. Aldrich, aka Fighteer I  |        fighteer AT cs DOT com         |
| Plan:  To find ANYONE willing to |   http://www.cs.com/fighteer   |
| play Descent 2 on DWANGO!        | Tagline: <this space for rent> |
---------------------------------------------------------------------

- Raw text -


  webmaster     delorie software   privacy  
  Copyright © 2019   by DJ Delorie     Updated Jul 2019