*.xml: Hyphenate `out of date`

This seems to be a compound adjective which usually gets a hyphen.

7 files changed, 20 insertions, 20 deletions

diff --git a/SCons/Environment.xml b/SCons/Environment.xml
index 9054c2e..9248721 100644
--- a/SCons/Environment.xml
+++ b/SCons/Environment.xml
@@ -513,7 +513,7 @@ env.Alias('update', ['file1', 'file2'], "update_database $SOURCES")
 <para>
 Marks each given
 <parameter>target</parameter>
-so that it is always assumed to be out of date,
+so that it is always assumed to be out-of-date,
 and will always be rebuilt if needed.
 Note, however, that
 &f-AlwaysBuild;
@@ -1339,7 +1339,7 @@ that specify a predefined decider function:
 <term><literal>"content"</literal></term>
 <listitem>
 <para>
-Specifies that a target shall be considered out of date and rebuilt
+Specifies that a target shall be considered out-of-date and rebuilt
 if the dependency's content has changed since the last time
 the target was built,
 as determined by performing a checksum
@@ -1361,7 +1361,7 @@ can still be used as a synonym, but is deprecated.
 <term><literal>"content-timestamp"</literal></term>
 <listitem>
 <para>
-Specifies that a target shall be considered out of date and rebuilt
+Specifies that a target shall be considered out-of-date and rebuilt
 if the dependency's content has changed since the last time
 the target was built,
 except that dependencies with a timestamp that matches
@@ -1398,7 +1398,7 @@ can still be used as a synonym, but is deprecated.
 <term><literal>"timestamp-newer"</literal></term>
 <listitem>
 <para>
-Specifies that a target shall be considered out of date and rebuilt
+Specifies that a target shall be considered out-of-date and rebuilt
 if the dependency's timestamp is newer than the target file's timestamp.
 This is the behavior of the classic Make utility,
 and
@@ -1412,7 +1412,7 @@ can be used a synonym for
 <term><literal>"timestamp-match"</literal></term>
 <listitem>
 <para>
-Specifies that a target shall be considered out of date and rebuilt
+Specifies that a target shall be considered out-of-date and rebuilt
 if the dependency's timestamp is different than the
 timestamp recorded the last time the target was built.
 This provides behavior very similar to the classic Make utility
@@ -3602,7 +3602,7 @@ Returns a Node object representing the specified &Python;
 Value Nodes can be used as dependencies of targets.
 If the string representation of the Value Node
 changes between &SCons; runs, it is considered
-out of date and any targets depending on it will be rebuilt.
+out-of-date and any targets depending on it will be rebuilt.
 Since Value Nodes have no filesystem representation,
 timestamps are not used; the timestamp deciders
 perform the same content-based up to date check.
diff --git a/SCons/Tool/javac.xml b/SCons/Tool/javac.xml
index b6b3f6e..af1fc31 100644
--- a/SCons/Tool/javac.xml
+++ b/SCons/Tool/javac.xml
@@ -364,7 +364,7 @@ env = Environment(JAVACCOMSTR="Compiling class files $TARGETS from $SOURCES")
                 that &SCons; expects will be generated by the &javac; compiler.
                 Setting &cv-JAVAVERSION; to a version greater than
                 <literal>1.4</literal> makes &SCons; realize that a build
-                with such a compiler is actually up to date.
+                with such a compiler is actually up-to-date.
                 The default is <literal>1.4</literal>.
             </para>
             <para>
diff --git a/doc/man/scons.xml b/doc/man/scons.xml
index 3477d2e..656d34c 100644
--- a/doc/man/scons.xml
+++ b/doc/man/scons.xml
@@ -800,7 +800,7 @@ This is the default behavior.</para>
 <para>If this mode is specified,
 all configuration tests will be re-run
 regardless of whether the
-cached results are out of date.
+cached results are out-of-date.
 This can be used to explicitly
 force the configuration tests to be updated
 in response to an otherwise unconfigured change
@@ -1067,7 +1067,7 @@ without requiring <filename>.py</filename> suffix.
 is prepared for building.
 &scons;
 prints this for each target it considers, even if that
-target is up to date (see also <option>--debug=explain</option>).
+target is up-to-date (see also <option>--debug=explain</option>).
 This can help debug problems with targets that aren't being
 built; it shows whether
 &scons;
@@ -1752,7 +1752,7 @@ if not GetOption("no_exec"):
 determine what would be built.  For example, if a file generated
 by a builder action is also used as a source in the build,
 that file is not available to scan for dependencies at all
-in an unbuilt tree, and may contain out of date information in a
+in an unbuilt tree, and may contain out-of-date information in a
 previously built tree.
 </para>
 <para>
@@ -1760,7 +1760,7 @@ previously built tree.
 as they would make changes to the filesystem
 (see &cv-link-CONFIGUREDIR; and &cv-link-CONFIGURELOG;).
 It can use stored information from a previous build,
-if it is not out of date,
+if it is not out-of-date,
 so a "priming" build may make subsequent no-exec runs
 more useful.
 </para>
@@ -1845,8 +1845,8 @@ The results may be analyzed using the &Python;
     <option>--question</option></term>
   <listitem>
 <para>Do not run any commands, or print anything.  Just return an exit
-status that is zero if the specified targets are already up to
-date, non-zero otherwise.</para>
+status that is zero if the specified targets are already up-to-date,
+non-zero otherwise.</para>
   </listitem>
   </varlistentry>
 
@@ -2827,7 +2827,7 @@ specified relationship into its internal dependency node graph,
 and only later makes the decision on whether anything is actually built,
 since this depends on command-line options,
 target selection rules, and whether the target(s) are
-out of date with respect to the sources.
+out-of-date with respect to the sources.
 </para>
 
 <para>
@@ -5685,7 +5685,7 @@ Aliases are virtual objects - they will not themselves result
 in physical objects being constructed, but are entered into
 the dependency graph related to their sources.
 An alias is checked for up to date by checking if
-its sources are up to date.
+its sources are up-to-date.
 An alias is built by making sure its sources have been built,
 and if any building took place,
 applying any Actions that are defined as part of the alias.
@@ -5707,7 +5707,7 @@ other alias has previously been created.
 The &f-link-Value; method returns a Value Node.
 Value nodes are often used for generated data that
 will not have any corresponding filesystem entry,
-but will be used to determine whether a build target is out of date,
+but will be used to determine whether a build target is out-of-date,
 or to include as part of a build Action.
 Common examples are timestamp strings,
 revision control version strings
diff --git a/doc/python10/summary.xml b/doc/python10/summary.xml
index a8f8767..0b61198 100644
--- a/doc/python10/summary.xml
+++ b/doc/python10/summary.xml
@@ -40,7 +40,7 @@
     This paper has introduced &SCons;, a next-generation build tool
     with a modular, embeddable architecture and a direct Python
     interface. &SCons; has a global view of the dependencies in a source
-    tree, uses MD5 signatures to decide if derived files are out of date,
+    tree, uses MD5 signatures to decide if derived files are out-of-date,
     and automatically scans files for dependencies, all of which make &SCons;
     builds exceptionally reliable. The &SCons; development methodology has
     been described, notable for its emphasis on automated regression
diff --git a/doc/user/build-install.xml b/doc/user/build-install.xml
index f0b400f..61dc1d8 100644
--- a/doc/user/build-install.xml
+++ b/doc/user/build-install.xml
@@ -155,7 +155,7 @@ Python 3.9.15
 
     <para>
     Recent versions of the Mac no longer come with &Python;
-    pre-installed; older versions came with a rather out of date
+    pre-installed; older versions came with a rather out-of-date
     version (based on &Python; 2.7) which is insufficient to run
     current &SCons;.
     The python.org installer can be used on the Mac, but there are
diff --git a/doc/user/depends.xml b/doc/user/depends.xml
index 23ae612..d408353 100644
--- a/doc/user/depends.xml
+++ b/doc/user/depends.xml
@@ -1001,7 +1001,7 @@ SetOption('implicit_cache', 1)
       external code that you use for compilation,
       the external header files will have changed
       and the previously-cached implicit dependencies
-      will be out of date.
+      will be out-of-date.
       You can update them by
       running &SCons; with the &implicit-deps-changed; option:
 
diff --git a/doc/user/make.xml b/doc/user/make.xml
index a14153f..b50cbd6 100644
--- a/doc/user/make.xml
+++ b/doc/user/make.xml
@@ -60,7 +60,7 @@ dependencies. Most often, an attempt is made to do a reasonable job of
 dependencies within a single directory, but no serious attempt is made to do
 the job between directories. Even when dependencies are working correctly,
 make's reliance on a simple time stamp comparison to determine whether a
-file is out of date with respect to its dependents is not, in general,
+file is out-of-date with respect to its dependents is not, in general,
 adequate for determining when a file should be rederived. If an external
 library, for example, is rebuilt and then ``snapped'' into place, the
 timestamps on its newly created files may well be earlier than the last