I am old-fashioned, but the first thing I do when diving into someone else's code is to print out the header files. Almost invariably it is more helpful to know what functions and declarations have been made ahead of time than anything else.
Also, it is important to remember that the original designers of a piece of code more than likely considered some of the same solutions that you might be considering when looking over their code, so it's wise to consider why they might not have done something, rather than just why they did something. Don't re-invent the wheel, only to have to invent it again. David Banker, Craig wrote: >Quick question to the fellow coders out there... > > >What do you do to bring yourself up to speed on complex coding projects? > >This one is very pertinant to those who want to contribute effort to open >source projects... > >Anybody care to share some insight or battle stories, perhaps? > > > >_______________________________________________ >General mailing list >[email protected] >http://brlug.net/mailman/listinfo/general_brlug.net > > >
