Quote:
Originally Posted by jsbjsb001
Yes, that's one of the biggest problems (maybe even the biggest) I have with trying to follow code. In that, if something, for example, is defined in a header and it's referenced in a c source file somewhere (or vica versa), then I've got to scan through the header to try and find what I'm looking at, and that's when I just get completely lost trying to find where I was up to in the c source file, then having to try and remember what I'd read beforehand, then try and follow the rest of the code. It's like trying to find my way through one of those hedge mazes where there is only one way out, but several dead ends, and I just keep hitting dead end, after dead end, if you know what I mean. And for that matter, even just in terms of c source files without looking at any header files it's pretty much the same story.
While if it helps in the meantime, where I can at least be able to follow code, I'm happy to give an IDE a go to develop enough skill to be able follow the code; I'd really like to be able to get to a point where I don't need to rely on an IDE, and just use the command-line like you.
|
You've got one or more distributions.
Go to the software manager and search the string "ide" it should find you some bunch of them. Common ones I've seen and heard about, Geany (I like), Codeblocks (heard a lot but never used), Eclipse (well ... I've used it, it does work as a full IDE, just ... I find it's very slow, takes a long time to load etc, but it is a full IDE and actually used quite a lot)
Or others.
What I can say about something like Geany, is that you can run it, open a few files. That's key, opening multiple files into tabs, just so you can swap from A to B easily.
Next it will be capable of searching either all open files, or if you make an actual project including those files, it will search "all project files"
The suggestion would be to use it on any code you've previously written, or write some "distributed across a few files code" and use it for those. I fully get that people learning may have all their code in one C and maybe one H file for each project they've done up to some point.
Other suggestion is to download some git project which contains a handful/dozen or two files (not hundreds) and give that a go just for driving/learning experience.
Yes there are more basic ones and with different ones you can build and debug all within them. Start with browsing code and then decide if you prefer also to set up building and debugging within them.
