diff options
Diffstat (limited to 'en_US.ISO8859-1/books/pmake/basics/chapter.sgml')
| -rw-r--r-- | en_US.ISO8859-1/books/pmake/basics/chapter.sgml | 8 |
1 files changed, 4 insertions, 4 deletions
diff --git a/en_US.ISO8859-1/books/pmake/basics/chapter.sgml b/en_US.ISO8859-1/books/pmake/basics/chapter.sgml index 5e96c33a1b..5439d225eb 100644 --- a/en_US.ISO8859-1/books/pmake/basics/chapter.sgml +++ b/en_US.ISO8859-1/books/pmake/basics/chapter.sgml @@ -93,7 +93,7 @@ <entry>If a colon is used, a target on the line is considered to be <quote>out-of-date</quote> (and in need of creation) if any of the sources has been modified - more recently than the target, or the target doesn't + more recently than the target, or the target does not exist. Under this operation, steps will be taken to re-create the target only if it is found to be out-of-date by using these two rules.<entry> @@ -114,7 +114,7 @@ <entry>If a double-colon is used, a target is <quote>out-of-date</quote> if any of the sources has been modified more recently than the target, or the - target doesn't exist, or the target has no sources. + target does not exist, or the target has no sources. If the target is out-of-date according to these rules, it will be re-created. This operator also does something else to the targets, but I will go into that @@ -330,7 +330,7 @@ Linking index</screen> occurred if one of the shells it invokes returns a non-zero status. When it detects an error, <application>PMake</application>'s usual action is to abort - whatever it's doing and exit with a non-zero status itself (any + whatever it is doing and exit with a non-zero status itself (any other targets that were being created will continue being made, but nothing new will be started. <application>PMake</application> will exit after the last job @@ -605,7 +605,7 @@ Linking index</screen> <literal>+=</literal> is the same as <literal>=</literal>, because the old value of the variable is sought only in the scope in which the assignment is taking place (for reasons of - efficiency that I won't get into here). <literal>:=</literal> + efficiency that I will not get into here). <literal>:=</literal> and <literal>?=</literal> will work if the only variables used are in the environment. <literal>!=</literal> is sort of pointless to use from the command line, since the same effect |