On Fri, Dec 26, 2014 at 10:24:27AM +0100, FRIGN wrote: > no matter how big the codebase is, in my opinion, if you need tools like > that there's something wrong with the code. And I've worked with really > big codebases (good and bad) in my time.
I'm talking about stuff like musl: I don't want to know that qsort() is defined in src/stdlib/sort.c. I just want to see the function. And if you're used to getting that in an instant, manually navigating it is just tedious. > You can get bigger than that, but a nice example is the ioquake3-engine, > which is very modular. > Modularity in general is what C is about and there's no reason to have > a very complex problem separated into several smaller problems instead > of writing one single big monolith you need ctags for to navigate. > See above. ctags() is useful even for small and suckless code bases. > It's no wonder the initial developer of ctags, Ken Arnold, is a die-hard > Java-proponent, a language we all know is designed to bloat problems up > unnecessarily. > Argumentum ad personam. Great! I'd rather discuss the meritts of ctags based on the program, please. Ciao, Markus
