From: "Michael Kerrisk (man-pages)" <mtk.manpages@gmail.com>
To: Alejandro Colomar <colomar.6.4.3@gmail.com>
Cc: mtk.manpages@gmail.com, linux-man@vger.kernel.org,
libc-alpha@sourceware.org
Subject: Re: [PATCH v2] regex.3: Add example program
Date: Sat, 17 Oct 2020 16:35:58 +0200 [thread overview]
Message-ID: <b9f5c938-4a00-0ced-5633-e00a57be252b@gmail.com> (raw)
In-Reply-To: <6d7ea902-357d-9581-83dc-fdeb14a592b4@gmail.com>
On 10/17/20 3:37 PM, Alejandro Colomar wrote:
> Oops, I should've used \e instead of \\ (see below).
> Please fix that :)
Applied and fixed. Thanks Alex!
Cheers,
Michael
> Alex
>
> On 10/17/20 3:27 PM, Alejandro Colomar wrote:
>> $ gcc -Wall -Wextra -Werror -pedantic regex.c -o regex
>> $ ./regex.3
>> String = "1) John Driverhacker;
>> 2) John Doe;
>> 3) John Foo;
>> "
>> Matches:
>> #0:
>> offset = 25; length = 7
>> substring = "John Do"
>> #1:
>> offset = 38; length = 8
>> substring = "John Foo"
>>
>> Signed-off-by: Alejandro Colomar <colomar.6.4.3@gmail.com>
>> ---
>>
>> Hi Michael,
>>
>> Now it's much better :)
>>
>> Cheers,
>>
>> Alex
>>
>> man3/regex.3 | 42 +++++++++++++++++++++++++++++++++++++++++++
>> 1 file changed, 42 insertions(+)
>>
>> diff --git a/man3/regex.3 b/man3/regex.3
>> index 7c5132995..72e576cc6 100644
>> --- a/man3/regex.3
>> +++ b/man3/regex.3
>> @@ -337,6 +337,48 @@ T} Thread safety MT-Safe
>> .TE
>> .SH CONFORMING TO
>> POSIX.1-2001, POSIX.1-2008.
>> +.SH EXAMPLES
>> +.EX
>> +#include <stdint.h>
>> +#include <stdio.h>
>> +#include <stdlib.h>
>> +#include <regex.h>
>> +
>> +#define ARRAY_SIZE(arr) (sizeof((arr)) / sizeof((arr)[0]))
>> +
>> +static const char *const str =
>> + "1) John Driverhacker;\en2) John Doe;\en3) John Foo;\en";
>> +static const char *const re = "John.*o";
>> +
>> +int main(void)
>> +{
>> + static const char *s = str;
>> + regex_t regex;
>> + regmatch_t pmatch[1];
>> + regoff_t off, len;
>> +
>> + if (regcomp(®ex, re, REG_NEWLINE))
>> + exit(EXIT_FAILURE);
>> +
>> + printf("String = \\"%s\\"\en", str);
>
>
> Here (twice)
>
>> + printf("Matches:\en");
>> +
>> + for (int i = 0; ; i++) {
>> + if (regexec(®ex, s, ARRAY_SIZE(pmatch), pmatch, 0))
>> + break;
>> +
>> + off = pmatch[0].rm_so + (s \- str);
>> + len = pmatch[0].rm_eo \- pmatch[0].rm_so;
>> + printf("#%d:\en", i);
>> + printf("offset = %jd; length = %jd\en", (intmax_t) off, (intmax_t) len);
>> + printf("substring = \\"%.*s\\"\en", len, s + pmatch[0].rm_so);
>
>
> And here (twice again)
>
>> +
>> + s += pmatch[0].rm_eo;
>> + }
>> +
>> + exit(EXIT_SUCCESS);
>> +}
>> +.EE
>> .SH SEE ALSO
>> .BR grep (1),
>> .BR regex (7)
>>
--
Michael Kerrisk
Linux man-pages maintainer; http://www.kernel.org/doc/man-pages/
Linux/UNIX System Programming Training: http://man7.org/training/
prev parent reply other threads:[~2020-10-17 14:36 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-17 13:13 [PATCH] regex.3: Add example program Alejandro Colomar
2020-10-17 13:17 ` Alejandro Colomar
2020-10-17 13:27 ` [PATCH v2] " Alejandro Colomar
2020-10-17 13:37 ` Alejandro Colomar
2020-10-17 14:35 ` Michael Kerrisk (man-pages) [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=b9f5c938-4a00-0ced-5633-e00a57be252b@gmail.com \
--to=mtk.manpages@gmail.com \
--cc=colomar.6.4.3@gmail.com \
--cc=libc-alpha@sourceware.org \
--cc=linux-man@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).