comparison man/maintaining.texi @ 43856:7d0cb2cc5e60

Use Cweb, not bison as an example of etags using #line.
author Francesco Potortì <pot@gnu.org>
date Tue, 12 Mar 2002 13:44:20 +0000
parents 16affaf7292b
children c1e620d6140c
comparison
equal deleted inserted replaced
43855:db463e67459c 43856:7d0cb2cc5e60
179 conventional name for a tags table file is @file{TAGS}. 179 conventional name for a tags table file is @file{TAGS}.
180 180
181 Each entry in the tags table records the name of one tag, the name of the 181 Each entry in the tags table records the name of one tag, the name of the
182 file that the tag is defined in (implicitly), and the position in that 182 file that the tag is defined in (implicitly), and the position in that
183 file of the tag's definition. When a file parsed by @code{etags} is 183 file of the tag's definition. When a file parsed by @code{etags} is
184 created from a different source file, like a C file created by 184 generated from a different source file, like a C file generated from a
185 @code{bison} from a source Yacc file, the tags of the parsed file 185 Cweb source file, the tags of the parsed file reference the source
186 reference the source file. 186 file.
187 187
188 Just what names from the described files are recorded in the tags table 188 Just what names from the described files are recorded in the tags table
189 depends on the programming language of the described file. They 189 depends on the programming language of the described file. They
190 normally include all file names, functions and subroutines, and may 190 normally include all file names, functions and subroutines, and may
191 also include global variables, data types, and anything else 191 also include global variables, data types, and anything else