Expand contractions.

This commit is contained in:
Joel Dahl 2006-02-08 16:17:09 +00:00
parent a16af69def
commit 6f2a1907f4
Notes: svn2git 2020-12-08 03:00:23 +00:00
svn path=/head/; revision=27062
3 changed files with 7 additions and 7 deletions

View file

@ -14,7 +14,7 @@
(and in &unix; in general) begin with a period
(<filename>.ms</filename>, <filename>.c</filename>, etc.).
Now, <application>PMake</application>'s idea of a suffix is more
like English's: it's the characters at the end of a word. With
like English's: it is the characters at the end of a word. With
this in mind, one possible solution to this problem goes as
follows:</para>

View file

@ -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

View file

@ -589,7 +589,7 @@ prog2 : $(PROG2OBJS) .INVISIBLE MAKEINSTALL</programlisting>
compile in the same directory along with, and at
the same time as, the program. You again have
the problem with ranlib that I mentioned
earlier, only this time it's more severe: you can not
earlier, only this time it is more severe: you can not
just put the ranlib off to the end since the
program will need those libraries before it can
be re-created. You can do something like this:
@ -1080,7 +1080,7 @@ MAKELIB : .USE
<listitem>
<para>This is identical to <literal>:M</literal> except
it substitutes all words that don't match the given
it substitutes all words that do not match the given
pattern.</para>
</listitem>
</varlistentry>