In article <1995Nov5.183814@miavx1>, [log in to unmask] (Kent Covert
) writes:
> Actually, there are several.  The blank lines are what are causing the
> problem.  DCL is fairly forgiving many times.  It lets you leave out
> the $ at the beginning of lines sometimes and lets you have blank lines in
> your program...sometimes.  This is one of those times, though, when you
> can't have blank lines.  The blank line is confusing the SET TERMINAL
> command.
 
Well, there goes one of the most useful things for making code readable....
Oh well; it doesn't seem to mind the rest, so I'll leave 'em in. I guess I
could use comments....
 
> Also, there is an easier way to debug programs that putting a lot of WRITE
> commands in it.  Try issuing the command SET VERIFY before running a .COM
> file (or add it to the beginning of your .COM file).  It'll show you all of
> the commands as they're being executed.  You can use the SET NOVERIFY
> command to turn this back off.
 
I was wondering how you did that... thanks.
 
--
Robert E. Williams, Jr. | The computer programmer's worst nightmare:
Macintosh Developer     |
Enterprise Software     |     Unwittingly finding compiler bugs.
___________________________________________________________________
[log in to unmask]          [log in to unmask]
[log in to unmask]            http://miavx1.muohio.edu/~williar2