AMBIGUITY
If a regular expression could match two different parts of the input string, it will match the one which begins earliest. If both begin in the same place but match different lengths, or match the same length in different ways, life gets messier, as follows. In general, the possibilities in a list of branches are considered in left-to-right order, the possibilities for ‘*’, ‘+’, and ‘?’ are considered longest-first, nested constructs are considered from the outermost in, and concatenated constructs are considered leftmost-first. The match that will be chosen is the one that uses the earliest possibility in the first choice that has to be made. If there is more than one choice, the next will be made in the same manner (earliest possibility) subject to the decision on the first choice. And so forth.
For example, '(ab|a)b*c' could match ‘abc’ in one of two ways. The first choice is between ‘ab’ and ‘a’; since ‘ab’ is earlier, and does lead to a successful overall match, it is chosen. Since the ‘b’ is already spoken for, the ‘b*’ must match its last possibility—the empty string—since it must respect the earlier choice.
In the particular case where no ‘|’s are present and there is only one ‘*’, ‘+’, or ‘?’, the net effect is that the longest possible match will be chosen. So 'ab*', presented with ‘xabbbby’, will match ‘abbbb’. Note that if 'ab*', is tried against ‘xabyabbbz’, it will match ‘ab’ just after ‘x’, due to the begins-earliest rule. (In effect, the decision on where to start the match is the first choice to be made, hence subsequent choices must respect it even if this leads them to less-preferred alternatives.)
RETURN VALUES
The regcomp function returns NULL for a failure ( regerror permitting), where failures are syntax errors, exceeding implementation limits, or applying ‘+’ or ‘*’ to a possibly-null operand.
SEE ALSO
ed(1), egrep(1), ex(1), expr(1), fgrep(1), grep(1), regex(3)
HISTORY
regexp(3),
BUGS
regexp(3),
