diff options
| author | наб <nabijaczleweli@nabijaczleweli.xyz> | 2023-04-21 02:39:47 +0200 |
|---|---|---|
| committer | Alejandro Colomar <alx@kernel.org> | 2023-04-21 03:35:42 +0200 |
| commit | 164297a322b5dee6addff9ad4acb224302ab6e7d (patch) | |
| tree | 87e7070305411b5b53fb0cbf7b11ce2f2b9e91ea | |
| parent | 1838a55edd6c47cbbc469b098fa1bd0fd1a5db1c (diff) | |
regex.3: Improve REG_STARTEND
Explicitly spell out the ranges involved. The original wording always
confused me, but it's actually very sane.
Remove "this doesn't change R_NOTBOL & R_NEWLINE" ‒ so does it change
R_NOTEOL? No. That's weird and confusing.
String largeness doesn't matter, known-lengthness does.
Explicitly spell out the influence on returned matches
(relative to string, not start of range).
Signed-off-by: Ahelenia Ziemiańska <nabijaczleweli@nabijaczleweli.xyz>
Signed-off-by: Alejandro Colomar <alx@kernel.org>
| -rw-r--r-- | man3/regex.3 | 29 |
1 files changed, 16 insertions, 13 deletions
diff --git a/man3/regex.3 b/man3/regex.3 index 47fe661d2..e91504986 100644 --- a/man3/regex.3 +++ b/man3/regex.3 @@ -131,23 +131,26 @@ compilation flag above). .TP .B REG_STARTEND -Use -.I pmatch[0] -on the input string, starting at byte -.I pmatch[0].rm_so -and ending before byte -.IR pmatch[0].rm_eo . +Match +.RI [ "string + pmatch[0].rm_so" , " string + pmatch[0].rm_eo" ) +instead of +.RI [ string , " string + strlen(string)" ). This allows matching embedded NUL bytes and avoids a .BR strlen (3) -on large strings. -It does not use +on known-length strings. +If any matches are returned +.RB ( REG_NOSUB +wasn't passed to +.BR regcomp (), +the match succeeded, and .I nmatch -on input, and does not change -.B REG_NOTBOL -or -.B REG_NEWLINE -processing. +> 0), they overwrite +.I pmatch +as usual, and the match offsets remain relative to +.I string +(not +.IR "string + pmatch[0].rm_so" ). This flag is a BSD extension, not present in POSIX. .SS Match offsets Unless |