Need to comprehend and utilize a good amount of code these days.
The overview–detail strategy applys everywhere.
As for object-oriented source written for a window application(I mean MFC, actually), maybe one good start point is the main window frame class. By checking the event handlers you can get a picture of how the application functions.
Another way is to start from analyzing the major data types, and the use of database. They are the target of processing.
The class tree view in IDE is of great help, i think:)
However, I found it very important to make notes. I just can remember that many data types, functions in a short time. I need a note to summarize what i’ve comphrended, and formuate a big picture. What’s more, i think it’s very unproductive if i sink into piles of code. i need to think about the whole picture, (maybe i can guess, at the beginning:)), and then formulate the main functionality from a top-down view. Then i can look into the code to check how the functionality is implemented. It’s much more productive when you’ve got a clear target when interpreting the source.
To summarize, i think generally there are 2 kinds of approaches. One is to start from the code, the other is to start from your own idea. And the process of interpreting itself, is to eliminate the gap between the 2.
Just some barbarian ideas. i’ve never received “formal education” in this concern.
i’m a barbarian programmer, i think. i yearn for instructions from you civilized ones:)