Fix typo in comment
possibe -> possible
This commit is contained in:
parent
b60bb6e2d6
commit
ca93ae5b1a
@ -242,7 +242,7 @@ EOF;
|
|||||||
* Paths that can match two or more routes, or have user-specified conditions are put in separate switch's cases.
|
* Paths that can match two or more routes, or have user-specified conditions are put in separate switch's cases.
|
||||||
*
|
*
|
||||||
* Last but not least:
|
* Last but not least:
|
||||||
* - Because it is not possibe to mix unicode/non-unicode patterns in a single regexp, several of them can be generated.
|
* - Because it is not possible to mix unicode/non-unicode patterns in a single regexp, several of them can be generated.
|
||||||
* - The same regexp can be used several times when the logic in the switch rejects the match. When this happens, the
|
* - The same regexp can be used several times when the logic in the switch rejects the match. When this happens, the
|
||||||
* matching-but-failing subpattern is excluded by replacing its name by "(*F)", which forces a failure-to-match.
|
* matching-but-failing subpattern is excluded by replacing its name by "(*F)", which forces a failure-to-match.
|
||||||
* To ease this backlisting operation, the name of subpatterns is also the string offset where the replacement should occur.
|
* To ease this backlisting operation, the name of subpatterns is also the string offset where the replacement should occur.
|
||||||
|
Reference in New Issue
Block a user