Darren Hiebert wrote:
> Thanks, Neil for offering such a lucid explanation.
'S'Okay - made sense for me to do it since I'd only just had to get it
straight myself! It's the sort of thing that's 'obvious' in retrospect!
> One item of note: You may wish to add the -n (--excmd=n) option ...
Good idea - I hadn't noticed that one. I see that my [heavily filtered]
Solaris 2.6 /usr/include tag file is 3.5Mb ...
--
=====================- http://www.racaldefence.com/ -====================
Neil Bird | If this .signature |
work mailto:neil.bird@... | looks pants, then | $> cd /pub
personal mailto:neil@... | stop using Outlook! | $> more beer

Neil Bird wrote:
> Basically, normal use allows one to follow a tag to the required *code*
> (be it a type definition or code subprogram) when, erm, coding.
>
> In this sort of case, however, one wants the subprogram *declaration*
> (or specification), since the code body's not available, and this is a
> different kettle of fish.
Thanks, Neil for offering such a lucid explanation.
One item of note: You may wish to add the -n (--excmd=n) option when
generating tag files from source code which is stable and not
subject to change, like /usr/include. This records the line numbers
of the tags instead of the regular expression, thus reducing the
size of the tag file considerably, which can make a huge difference
for something like /usr/include.
The reason that ctags normally records regular expressions is so
that the tags can still be found even as the source code changes,
reducing the necessity of frequently regenerating the tag file.
--
Darren Hiebert <darren@...>
http://darren.hiebert.com