[dstarfire]

I can read and understand most code (even if I don't understand what every line does, I can get a general idea of what's going on). However, I'm rather lost with projects where the code is broken up into multiple files, referencing each other and frequently arranged in some hierarchical structure.

Is there a standard for how this stuff is broken up? How can I find which file/s contain the function I want to modify? I'd like to go in and tinker with stuff, but I don't want to learn the entire language and every toolkit and library used by a program.

[linuxrants7xpg]

It all depends on who wrote the code really. Just read the includes first. Familiarize yourself with those, and make yourself an index. Which file has which functions and brief summary of what they do just long enough for you to remember. Should get you what you need to know.

[dstarfire]

linuxrants7xpg, on 15 July 2012 - 10:00 PM, said:

It all depends on who wrote the code really. Just read the includes first. Familiarize yourself with those, and make yourself an index. Which file has which functions and brief summary of what they do just long enough for you to remember. Should get you what you need to know.

Thanks. I didn't even think to look over the includes. That'll at least help me figure out the hierarchy and how functions are grouped/arranged.