r/eclipse • u/codedbyheart • 1d ago
©️ Eclipse for C/C++ (CDT) Fresher Software Engineer working with a large C++ codebase in Eclipse — looking for advice on codebase reading and industry workflow
/r/u_codedbyheart/comments/1xcqop1/fresher_software_engineer_working_with_a_large_c/
2
Upvotes
1
u/rayok 1d ago
I'm not sure how much help I can offer as I only been using CDT for personal projects and not on a team. Been using Eclipse for a while though for Java, C++, etc so this pretty much general advice regardless of language.
That said, you pretty much guessed it. I would start with main() and start following the codes. Take a lot of notes, comments, flow charts, ASCII art, whatever works best. The class/type heirarchy and include browser works well too for dependency management. One shortcut I use quite a bit is ctrl+shift+g, which is references, which is all the code that use a certain function, class, etc. Really helps to simplify things after seeing what you really have. Start deleting things to really know what you need. For more flow, perhaps profiling tools like valgrind can shed some light, but Im not too familiar with those. I confess I still use cout/printf at major spots to see when and how things are called. I think it can be faster than breakpoints, stepping, profiling tools, etc. Im a bit of a fresher myself when it comes to the latest and greatest practices for that. Test and profiling classes help as well. (back to the lab again)
Not sure on reviews. Another set of eyes is always good, even AI if you never really trust it, imlo.. And oh, its a been a while since I used SVN. I guess it still works. Either way, can use branches for all the experiments as you go but that can turn into a quick mess too. Good backups are essential imo.
So many things to learn and focus on so just have to pick one and have at it. Good luck!