| 1 | .TH CTAGS UCB 2/24/79 UCB |
| 2 | .SH NAME |
| 3 | ctags \- compute a tags file for a C program |
| 4 | .SH SYNOPSIS |
| 5 | .B ctags |
| 6 | name ... |
| 7 | .SH DESCRIPTION |
| 8 | .I Ctags |
| 9 | makes a tags file for |
| 10 | .IR ex (UCB) |
| 11 | from the specified C programs. |
| 12 | A tags file gives the locations of specified objects (in this case |
| 13 | functions) in a group of files. |
| 14 | Each line of the tags file contains the function name, |
| 15 | the file in which it is defined, and a scanning pattern used to find |
| 16 | the function definition. These are given in separate fields on the line, |
| 17 | separated by blanks or tabs. |
| 18 | .SH FILES |
| 19 | .DT |
| 20 | tags output tags file |
| 21 | .SH SEE ALSO |
| 22 | astags(UCB), ex(UCB), vi(UCB) |
| 23 | .SH BUGS |
| 24 | This tags program is a primitive shell script, and requires functions |
| 25 | to be recognizable by their starting in the first column of |
| 26 | input lines on lines ending with a `)'. |
| 27 | .PP |
| 28 | No way to use it to incrementally update a tags file. |
| 29 | In a |
| 30 | .I makefile, |
| 31 | we could move the |
| 32 | .I tags |
| 33 | file away and then use |
| 34 | .I sort |
| 35 | and |
| 36 | .I uniq |
| 37 | to get around this. |
| 38 | .PP |
| 39 | For tags to be more useful, a good |
| 40 | .I ctags |
| 41 | program is needed which references external and macro definitions in |
| 42 | header files as well as being less sensitive to formatting. |