Re: COUNTING LINES OF CODE

When disk space allows, I store on-line the source code associated with the 
original base package before any modifications & when a never before modified 
program is desired to be modified, I go to this library.

I have a library of modified in production
I have a library of modified in testing & development

Along comes a new release from the original vendor.
In some cases they have updated the same programs that we have modified,
I now have to use PDM-54 to compare what exactly they changed from their last 
version, because they do not exactly adhere to their own documentation rules.
I also use PDM-54 to see the aggregate of our modifications.
This gives me the sections of code that need a merger of the two efforts.

Now in your case, you could use PDM-54 to compare your production code to the 
original code & this would give you a line count, by program, that someone 
altered.

A bit messy, but a start.

However, it might be smart to tell them that you will have to do some 
programming to get at this information & to ask what kind of time budget you 
have to do a good job of fulfilling this user request.  For example, is it 
more important than your other duties?

This will determine if it is a stupid whim because someone read some place 
some theory that has long since been proven false that there is a 
relationship between volume & quality, or if they really know what they are 
doing with this data.  Even if it is a stupid whim, you may have to do it, 
but it might be easier to put the tools into the user hands ... let them see 
the code which is totally greek to them, while they put the PDM-54 counts 
into a spread sheet that has totals by program.

MacWheel99@aol.com (Alister Wm Macintyre) (Al Mac)

>  From:    barsa@barsaconsulting.com
>  
>  Angie,
>  
>  You have two questions:
>  
>  1.   How do to this?
>  2.   Why is it important?
>  
>  1.   How to do this?
>  
>  If you wrote all of your own modifications in your own library, DSPFD
>  *MBRLIST of the source files will do the job.  If you made modifications to
>  their code, and worked in their library structure, this is tough.  You
>  could determine when the last modification date to their software was, and
>  then write your own code to find the number of lines of code that you
>  changed/added, but this is not trivial.
>  
>  2.   Why is this important?
>  
>  They probably want to know how extensive your changes are.
>  
>  Al



+---
| This is the Midrange System Mailing List!
| To submit a new message, send your mail to MIDRANGE-L@midrange.com.
| To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com.
| To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator: david@midrange.com
+---