Slick EDIT V3.3 - Manual (Page 94)

• Other Extension-Specific Tag Categories - The tag files listed under each of the other language-spe-
cific categories apply to that language only. Use these categories to add tag files for third-party librar-
ies.
Tag File Search Order
When doing tag lookups, the tag files are searched in a specific order, which affects the tags found. The
following are examples of the order in which tag files are searched.
Example: Java Tag File Search Order
If a Java source file is open, when a tagging-related operation is performed, the tag files are searched in
the following order:
1. Workspace tag file, providing it contains other Java source files.
2. Auto-updated tag files containing other Java source files.
3. The "Java" Compiler Configuration tag file corresponding to the Java environment specified for your
project.
4. Extension-specific Java tag files, in the order that they are listed in the Context Tagging - Tag Files
Dialog .
Example: C/C++ Tag File Search Order
If a C/C++ source file is open, when a tagging-related operation is performed, the tag files are searched in
the following order:
1. Workspace tag file, providing it contains other C/C++ source files.
2. Auto-updated tag files containing other C/C++ source files.
3. The "C" Compiler Configuration tag file corresponding to your default C compiler configuration as spe-
cified in your project (C/C++ Refactoring
→
C/C++ Compiler Options), or global default.
4. Extension-specific C tag files, in the order that they are listed in the Context Tagging - Tag Files Dialog .
Note that if you have a "C" Compiler Configuration tag file, cpp.vtg will be excluded from this list.
Rebuilding Tag Files
The Rebuild Tag File dialog box contains options for rebuilding the selected file. To display the Rebuild
Tag File dialog, click Tools
→
Tag Files. When the Context Tagging - Tag Files Dialog is displayed, se-
lect a file to rebuild, then click Rebuild Tag File.
Figure 5.10. Rebuild Tag File Dialog
Managing Tag Files
72