Changeset 11599 for trunk/libtransmission/wildmat.c

Timestamp:

Dec 27, 2010, 7:18:17 PM (10 years ago)

Author:

charles

Message:

(trunk) Join the 21st century and use only 1 space at the end sentences. This commit is nearly as important as the semi-annual ones that remove trailing spaces from the ends of lines of code... :)

File:

• trunk/libtransmission/wildmat.c (modified) (4 diffs)

trunk/libtransmission/wildmat.c

@@ -4 +4 @@
 **  Do shell-style pattern matching for ?, \, [], and * characters.
 **  Might not be robust in face of malformed patterns; e.g., "foo[a-"
-**  could cause a segmentation violation.  It is 8bit clean.
+**  could cause a segmentation violation. It is 8bit clean.
 **
 **  Written by Rich $alz, mirror!rs, Wed Nov 26 19:03:17 EST 1986.
@@ -12 +12 @@
 **
 **  Special thanks to Lars Mathiesen <thorinn@diku.dk> for the ABORT code.
-**  This can greatly speed up failing wildcard patterns.  For example:
+**  This can greatly speed up failing wildcard patterns. For example:
 **      pattern: -*-*-*-*-*-*-12-*-*-*-m-*-*-*
 **      text 1:  -adobe-courier-bold-o-normal--12-120-75-75-m-70-iso8859-1
 **      text 2:  -adobe-courier-bold-o-normal--12-120-75-75-X-70-iso8859-1
-**  Text 1 matches with 51 calls, while text 2 fails with 54 calls.  Without
-**  the ABORT, then it takes 22310 calls to fail.  Ugh.  The following
+**  Text 1 matches with 51 calls, while text 2 fails with 54 calls. Without
+**  the ABORT, then it takes 22310 calls to fail. Ugh. The following
 **  explanation is from Lars:
 **  The precondition that must be fulfilled is that DoMatch will consume
-**  at least one character in text.  This is true if *p is neither '*' nor
+**  at least one character in text. This is true if *p is neither '*' nor
 **  '\0'.)  The last return has ABORT instead of FALSE to avoid quadratic
-**  behaviour in cases like pattern "*a*b*c*d" with text "abcxxxxx".  With
+**  behaviour in cases like pattern "*a*b*c*d" with text "abcxxxxx". With
 **  FALSE, each star-loop has to run to the end of the text; with ABORT
 **  only the last one does.
@@ -29 +29 @@
 **  instance will return either TRUE or ABORT, and any calling instance
 **  will therefore return immediately after (without calling recursively
-**  again).  In effect, only one star-loop is ever active.  It would be
+**  again). In effect, only one star-loop is ever active. It would be
 **  possible to modify the code to maintain this context explicitly,
 **  eliminating all recursive calls at the cost of some complication and
 **  loss of clarity (and the ABORT stuff seems to be unclear enough by
-**  itself).  I think it would be unwise to try to get this into a
+**  itself). I think it would be unwise to try to get this into a
 **  released version unless you have a good test data base to try it out
 **  on.
@@ -111 +111 @@
 
 /*
-**  User-level routine.  Returns TRUE or FALSE.
+**  User-level routine. Returns TRUE or FALSE.
 */
 int