John Eells wrote:
>What's a "line of code"? That's a serious question.
Indeed!
Oh, BTW, How many code of lines do you need to write a program to define this
term? ;-D
>Is a line of assembler equivalent to a line of PLX, C, REXX, Java, ISPF DTL?
>etc.
It depends, but it is not likely, because compilers sometimes add overhead
statements (garbage collection or saving status of runtime environment or
variables or debug statements) in the object code between your source lines.
... or compilers may remove 'dead code', for example a function which is never
called at all.
Do you count these 'dead code' source lines too?
If you write a high level language and repeat the same logic in Assembler, your
high level code may contains more statements than your compact Assembler code.
How long is that line and how many statements can you squeeze in one line?
Is this one line (pseudo code)
x=0;for i=1 to 100;do x=x+i;end;print x;exit
... the same as this neatly one of 9 lines in total?
x=0
for i=1 to 100
do
x=x+i
end
print x
exit
>Are comment lines included in the count?
Who cares? ;-D Comments are for lazy wannabee programmers. ;-)
>Perpaps the best thing to compare is the size of the binaries on disk, but
>even that begs the question of "what's an executable"? Do ISPF panels, for
>example, count?
What about PARMLIB members (for runtime options for example) or ISPF skeleton
libraries? Or in OMVS, some folders for various things like pictures (to be
displayed on your HTTPS server) ? etc.
... or Assembler macros? Do they count if you ship them together with your
program(s)?
Good questions, John. Thanks!
Groete / Greetings
Elardus Engelbrecht
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [email protected] with the message: INFO IBM-MAIN
