Lines Matching refs:by
13 suggested by Martin Richards. These were not Unix-like in form, and were quite
14 restricted in what they could do by comparison with Perl. The interesting part
17 not operate by backtracking, as the original Henry Spencer code and current
18 Perl code does, but instead checked all possibilities simultaneously by keeping
31 By contrast, the code originally written by Henry Spencer (which was
35 the original library.) The execution function operates by backtracking and
46 that used an amount of store bounded by a multiple of the number of characters
68 Up to and including release 6.7, PCRE worked by running a very degenerate first
99 system stack used by pcre_compile(). This is a safety feature for environments
100 with small stacks where the patterns are provided by users.
139 is handled entirely at compile time by generating different opcodes for the
201 OP_FAIL ) parentheses, it may be preceded by one or more
202 OP_PRUNE ) OP_CLOSE, each followed by a count that
214 OP_MARK is followed by the mark name, preceded by a one-unit length, and
215 followed by a binary zero. For (*PRUNE), (*SKIP), and (*THEN) with arguments,
223 The OP_CHAR opcode is followed by a single character that is to be matched
250 Each opcode is followed by the character that is to be repeated. In ASCII mode,
262 Each of these is followed by a count and then the repeated character. OP_UPTO
264 fixed maximum is coded as an OP_EXACT followed by an OP_UPTO (or OP_MINUPTO or
295 Match by Unicode property
299 character by testing its Unicode property (the \p and \P escape sequences).
300 Each is followed by two units that encode the desired property as a type and a
306 Repeats of these items use the OP_TYPESTAR etc. set of opcodes, followed by
324 negative one. In either case, the opcode is followed by a 32-byte (16-short,
335 are less than 256, followed by a list of pairs (for a range) and single
338 OP_XCLASS is followed by a unit containing flag bits: XCL_NOT indicates that
358 OP_REF (caseful) or OP_REFI (caseless) is followed by a count containing the
359 reference number if the reference is to a unique capturing group (either by
360 number or by name). When named groups are used, there may be more than one
361 group with the same name. In this case, a reference by name generates OP_DNREF
362 or OP_DNREFI. These are followed by two counts: the index (not the byte offset)
363 in the group name table of the first entry for the requred name, followed by
389 followed by the minimum and maximum repeat counts.
404 3.5, the limit was removed by putting the bracket number into the data for
408 A bracket opcode is followed by LINK_SIZE bytes which give the offset to the
410 OP_KET opcode. Each OP_ALT is followed by LINK_SIZE bytes giving the offset to
416 respectively (see below for possessive repetitions). All three are followed by
421 is preceded by one of OP_BRAZERO, OP_BRAMINZERO, or OP_SKIPZERO. These are
449 When a repeated group (capturing or non-capturing) is marked as possessive by
452 of OP_SCBRA. The end of such a group is marked by OP_KETRPOS. If the minimum
453 repetition is zero, the group is preceded by OP_BRAPOSZERO.
478 is OP_REVERSE, followed by a count of the number of characters to move back the
492 subpattern using the opcode OP_CREF followed by a count containing the
494 If the reference was by name and there is more than one group with that name,
495 OP_DNCREF is used instead. It is followed by two counts: the index in the group
510 OP_RECURSE is followed by aLINK_SIZE value that is the offset to the starting
520 OP_CALLOUT is followed by one unit of data that holds a callout number in the
