If you want to find the flow of the code, you can use cscope . http://cscope.sourceforge.net/cscope_vim_tutorial.html
On Wed, Jan 14, 2015 at 2:02 PM, Chirag Anand <[email protected]> wrote: > On 14 January 2015 at 11:35, Great Avenger Singh <[email protected]> > wrote: > > What could be the best Method/Way to explore the source code of any > > "Open source project" that how the flow of code works. > > 1. Find a specific problem to solve. Look at bug-trackers, mailing > lists, or from your own requirement (works best). > 2. Download the source code. > 3. 'grep' the keywords. > 4. Look at the header files and documentation to understand the > API/functions. > 5. Understand the related code. > 5. Jump in and start modifying, compiling, looking at the output etc. > > This is just a crude way of jumping into a project's source code if > that's what you are looking for. As other people mentioned, the better > way may be to talk to people, read blogs, figure out your interest in > the project etc. (and probably not try to find an algo). :) > > HTH. > > -- > Chirag Anand > http://atvariance.in/chiraganand > > -- > -- > Mailing list guidelines and other related articles: > http://lug-iitd.org/Footer > > --- > You received this message because you are subscribed to the Google Groups > "Linux User Group @ IIT Delhi" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > For more options, visit https://groups.google.com/d/optout. > -- Pradeep Kumar Mahato -- -- Mailing list guidelines and other related articles: http://lug-iitd.org/Footer --- You received this message because you are subscribed to the Google Groups "Linux User Group @ IIT Delhi" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
