public inbox for glibc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "gilles.duvert@univ-grenoble-alpes.fr" <sourceware-bugzilla@sourceware.org>
To: glibc-bugs@sourceware.org
Subject: [Bug libc/30024] regcomp does not honour the documented behaviour.
Date: Thu, 19 Jan 2023 11:18:18 +0000	[thread overview]
Message-ID: <bug-30024-131-mhbk4WxkX0@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-30024-131@http.sourceware.org/bugzilla/>

https://sourceware.org/bugzilla/show_bug.cgi?id=30024

--- Comment #2 from Gilles Duvert <gilles.duvert@univ-grenoble-alpes.fr> ---
man 7 regex excerpt:
REGEX(7)                                                                       
                        Linux Programmer's Manual                              
                                                                 REGEX(7)

NAME
       regex - POSIX.2 regular expressions

and man 3 regcomp says:
REGEX(3)                                                                       
                        Linux Programmer's Manual                              
                                                                 REGEX(3)

NAME
       regcomp, regexec, regerror, regfree - POSIX regex functions


so, POSIX, POSIX.2 ??

-- 
You are receiving this mail because:
You are on the CC list for the bug.

  parent reply	other threads:[~2023-01-19 11:18 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-01-18 23:02 [Bug libc/30024] New: " gilles.duvert@univ-grenoble-alpes.fr
2023-01-18 23:26 ` [Bug libc/30024] " schwab@linux-m68k.org
2023-01-19 11:18 ` gilles.duvert@univ-grenoble-alpes.fr [this message]
2023-01-19 15:36 ` schwab@linux-m68k.org
2023-01-19 22:21 ` gilles.duvert@univ-grenoble-alpes.fr

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=bug-30024-131-mhbk4WxkX0@http.sourceware.org/bugzilla/ \
    --to=sourceware-bugzilla@sourceware.org \
    --cc=glibc-bugs@sourceware.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 read-only IMAP folder(s) and NNTP newsgroup(s).