>> One of the first things I do is instrument each method and function, so
> I can trace program flow >in the debugger. This is handy both to see
> what is called, and when, as well as (occasionally)
>> to determine where slowdowns are occurring.
>
> Can you expand on what you mean about 'instrument each method and
> function' to trace the program flow?
At the top of each method/function, put a line like
debugo "customer.init() is executing"
debugo "lib.encrypt() is executing"
That sort of thing.
>> What types of things to do you after getting a mess-o-code dumped in
> your lap? We're assuming,
>> of course, that the documentation consists of well, you know. Hopefully
> you've found the
>> MAIN.PRG, and have all of the code, but let's not assume anything past
> that.
>
> One challenge I have had at this job is when I do a build is to make
> sure I have all of the programs. Previous developers like to share the
> programs but if you are not pathed correctly the project manager gets
> lost and I have dig through the hard drive trying to find the little
> prgs all over the place. Such fun!
That's another item on my list - setting up the dev environment
appropriately. Lots of different variations - some apps still have their
data in a \data subdir off the exe... or worse, in the same dir as the exe.
Of course, if you have that problem (prgs all over the place), it's time
to create a centralized library, and then to install version control, eh?
Whil
_______________________________________________
Post Messages to: [email protected]
Subscription Maintenance: http://leafe.com/mailman/listinfo/profox
OT-free version of this list: http://leafe.com/mailman/listinfo/profoxtech
** All postings, unless explicitly stated otherwise, are the opinions of the
author, and do not constitute legal or medical advice. This statement is added
to the messages for those lawyers who are too stupid to see the obvious.
