>>>>>>>>>>The software metrics folks are at it again! They want a Lines of Code count from FoxPro. Any suggestions on an easy way to determine this?
>>>>>>>>>>
>>>>>>>>>>Loyd
>>>>>>>>>
>>>>>>>>>Loyd
>>>>>>>>>
>>>>>>>>>If it's FPD or FPW, use FoxDoc. Ask for the System Report. That will go through and count the lines of code for you. VFP is gonna be a bit of a pain, since FoxDoc no longer exists for it and the 'Documenting Wizard' is a joke as far as I can tell. You can set up a program that will open your forms as a database and then count the lines of code in the Memos. but that can also be a bit of a pain. Last time we had to come up with a count, it was for that happy 'Year 2000' bit.
>>>>>>>>
>>>>>>>>
>>>>>>>>how would you count lines of code in objects that use inheritance and other OO methods?
>>>>>>>
>>>>>>>Personally, I'd do it the same way, and include those counts on systems that used the particular object. It wouldn't take too much to dump those numbers into a .dbf and then reference that table during the count (Form XYZ calls class ABC (120 lines from linecnt.dbf) and then adds 10 more lines).
>>>>>>>
>>>>>>>My next step would be to sit those Lovely people down and explain to them that the concept of "lines of code" is becoming outdated and borderline impossible to do. If that fails, I figure a good, solid closet, stout rope and some ceiling hooks will handle the problem (Tie 'em up, hang 'em up, close and lock the door).
>>>>>>
>>>>>>Yes! A Tejas women -- Alright! (g).
>>>>>>
>>>>>>The alternative is to sit them down & spend hours using words they won't understand. Out of sheer boredom & the thought of you wasteing their time they will give up & accept your explanations.
>>>>>>
>>>>>>Or else you can download stacks of White Papers & put a 1' tall stack of paper on their desk & say -- that's why I can't. (g)
>>>>>>
>>>>>>Tom
>>
>>Or you can make up a number. If they don't believe you you can tell them how to edit classes & look at the code. That should throw them off the trail! (s)
>>
>>Tom
>>
>>>>>You mean words like "diminishing returns", "mismanagement of resources", "depreciation of value per unit of time"...words like that? Can you tell I've spent WAY too much time around accountants?
>>>>>
>>>>>I actually did get into a 'PMail War' with one once. I asked them to decide if I should count the lines of code in an oft used procedure once, or add them in everytime I issued a "Do procname". I think it confoozed them.....
>>>>
>>> You could tell the beancounters that the lines of code very depending on the events triggered by the user.
>ROFL That's the best answer so far!
>Another 'low cost' solution is to find out what they expect you to produce in whatever time period they're using and use a random number generator to generate a random number that is within the range they expect.
>
>Or always give them a number like 1165.426 - when they complain about the decimals explain that you counted partially completed lines as fractions :)
>
>Have fun and annoy them -- it's good for them :)
>Jen

Or, as a friend of mine once said: "The system is 14367 lines of code, but only one line is being used at any given time"