Re: Line-by-line commenting in source code

Also the ifs could be there to be sure the lines of code never execute.  One
reason a programmer might have done this before the days of the D spec is
that fields may be defined here but not used here.  Another might be left
over debugging code.  What easier way is there to remove a whole block of
code from running when one is chasing down an elusive bug?
 
 
 
---------------------------------------------------------
Booth Martin   http://www.MartinVT.com
Booth@xxxxxxxxxxxx
---------------------------------------------------------
 
-------Original Message-------
 
From: Midrange Systems Technical Discussion
Date: 02/27/04 08:26:44
To: Midrange Systems Technical Discussion
Subject: Re: Line-by-line commenting in source code
 
Rob,
 
>The if's confuse me.
 
Those type of lines have been known to be used by vendors to "salt" program
code
to help substantiate copying of code, as it is otherwise unlikely a "clean
room"
approach to performing the same process would include the same lines.  If
this
is the reason it exists, that would also explain the lack of comments about
its
inclusion.
 
I have also seen similar IF tests code with a conditioning indicator, in
code
which began in RPG II on the S36.  Since it does not support *INxx, you can
t
test the indicator itself with an IF statement.  So one work-around is to
use a
conditioning indicator with an otherwise always true IF expression just so
you
can condition a block of code on a single indicator test.
 
Doug