summaryrefslogtreecommitdiff
path: root/doc/user/scanners.xml
diff options
context:
space:
mode:
Diffstat (limited to 'doc/user/scanners.xml')
-rw-r--r--doc/user/scanners.xml3
1 files changed, 1 insertions, 2 deletions
diff --git a/doc/user/scanners.xml b/doc/user/scanners.xml
index 1e2234257..9a0a1d34a 100644
--- a/doc/user/scanners.xml
+++ b/doc/user/scanners.xml
@@ -146,14 +146,13 @@ over the file scanning rather than being called for each input line:
<para>
- &SCons; has routines that know how to look in
+ &SCons; has built-in &Scanners; that know how to look in
C/C++, Fortran, D, IDL, LaTeX, Python and SWIG source files
for information about
other files that targets built from those files depend on -
for example, in the case of files that use the C preprocessor,
the <filename>.h</filename> files that are specified
using <literal>#include</literal> lines in the source.
- Such a routine is called a <firstterm>&Scanner;</firstterm>.
You can use the same mechanisms that &SCons; uses to create
its built-in Scanners to write Scanners of your own for file types
that &SCons; does not know how to scan "out of the box."