Path: utzoo!utgpu!water!watmath!clyde!att!osu-cis!tut.cis.ohio-state.edu!mailrus!ames!pasteur!ucbvax!dewey.soe.berkeley.edu!oster
From: oster@dewey.soe.berkeley.edu (David Phillip Oster)
Newsgroups: comp.sys.mac.programmer
Subject: Re: C topics. (really ctags)
Message-ID: <26431@ucbvax.BERKELEY.EDU>
Date: 14 Oct 88 08:30:29 GMT
References: <10389@dartvax.Dartmouth.EDU> <10403@dartvax.Dartmouth.EDU>
Sender: usenet@ucbvax.BERKELEY.EDU
Reply-To: oster@dewey.soe.berkeley.edu.UUCP (David Phillip Oster)
Organization: School of Education, UC-Berkeley
Lines: 25

Most of what ctags does for you is already done by LightSpeed C.  If you
command-double click on an identifer in LightSpeed C, it opens the file
where the identifier is defined and searches for it.

+ for ctags:
o.  ctags starts searching at the line given in the tags file, so it is more
likely to find the correct occurence of the identifier, for it actually to
be the definition.

o. ctags will find definitions of macros, not just of procedures and
variables.

- for ctags
o. you must use an editor that supports tag files.
o. you must periodically run a separate application program to update your
tag file.

Just as LightSpeed C automatically does a good portion of "make", but the
unix make has more power and takes more work, so LightSpeed C
automatically does a good portion of the work of ctags, but the unix
version has more power and takes more work.

--- David Phillip Oster            --When you asked me to live in sin with you
Arpa: oster@dewey.soe.berkeley.edu --I didn't know you meant sloth.
Uucp: {uwvax,decvax,ihnp4}!ucbvax!oster%dewey.soe.berkeley.edu