On Fri, 26 Dec 2014 09:59:02 +0100
Markus Wichmann <nullplan_AT_gmx.net> wrote:
Hey Markus,
> ctags tells me the place where all the functions are defined. It also
> tells me where all the defines are and where all the structure members
> are. It tells me the location of the tag types and the typedefs and so
> on. All of that is available to me using a single shell command and a
> single button press in vim. OK, that last one was a lie, because the
> default button combination for "follow tag" is <C-]>, which I have to
> type as CTRL-ALT GR-9 on Linux and CTRL-+ on Windows. But the point
> remains.
>
> How many search commands do you have to memorize? If you want to even
> just read the code of another project, maybe even a big one, how many
> sed-scripts do you have to run over the existing code base in order to
> navigate? Or even programs? Or are you content with only reading the
> code you directly control the style of?
>
> Nothing against minimal solutions, I like those. But they have to
> actually solve the problem without creating equally big new ones.
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.
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.
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.
Cheers
FRIGN
--
FRIGN <dev_AT_frign.de>
Received on Fri Dec 26 2014 - 10:24:27 CET