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
Subject: Re: [PATCH] regex.3: Remove unnecessary include
Date: Sun, 11 Oct 2020 07:43:49 +0200 [thread overview]
Message-ID: <56cbf4c7-6a5c-2e36-1c58-6f452e4f8097@gmail.com> (raw)
In-Reply-To: <20201010175001.3818-1-colomar.6.4.3@gmail.com>
On 10/10/20 7:50 PM, Alejandro Colomar wrote:
> POSIX requires that the <regex.h> header shall define
> the structures and symbolic constants used by the
> regcomp(), regexec(), regerror(), and regfree() functions.
>
> Therefore, there should be no need to include <sys/types.h> at all.
Thanls, Alex. Patch applied.
Cheers,
Michael
> The POSIX docs don't use that include:
> https://pubs.opengroup.org/onlinepubs/9699919799/functions/regcomp.html
>
> Signed-off-by: Alejandro Colomar <colomar.6.4.3@gmail.com>
> ---
> man3/regex.3 | 1 -
> 1 file changed, 1 deletion(-)
>
> diff --git a/man3/regex.3 b/man3/regex.3
> index d4f7a09e7..414011d91 100644
> --- a/man3/regex.3
> +++ b/man3/regex.3
> @@ -32,7 +32,6 @@
> regcomp, regexec, regerror, regfree \- POSIX regex functions
> .SH SYNOPSIS
> .nf
> -.B #include <sys/types.h>
> .B #include <regex.h>
> .PP
> .BI "int regcomp(regex_t *" preg ", const char *" regex ", int " cflags );
>
--
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-11 5:43 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-10 17:50 [PATCH] regex.3: Remove unnecessary include Alejandro Colomar
2020-10-10 18:10 ` Alejandro Colomar
2020-10-11 5:44 ` Michael Kerrisk (man-pages)
2020-10-11 5:43 ` 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=56cbf4c7-6a5c-2e36-1c58-6f452e4f8097@gmail.com \
--to=mtk.manpages@gmail.com \
--cc=colomar.6.4.3@gmail.com \
--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).