public inbox for glibc-bugs-regex@sourceware.org help / color / mirror / Atom feed
From: "rrt at sc3d dot org" <sourceware-bugzilla@sourceware.org> To: glibc-bugs-regex@sources.redhat.com Subject: [Bug regex/11857] New: Missing documentation in regex.h Date: Fri, 30 Jul 2010 09:15:00 -0000 [thread overview] Message-ID: <20100730091503.11857.rrt@sc3d.org> (raw) The attached patch addresses the following deficiencies in regex.h's documentation: 1. It mentions that re_compile-allocated pattern buffers should be freed with regfree. (This may seem surprising, as regfree is in the POSIX API, not the GNU API. Eric Blake, 20 Jul 10, wrote to bug-gnulib@gnu.org: Odd or not, that is the correct usage pattern. regfree() is the correct way to release memory allocated by re_compile. ) 2. It explains that when using regfree, the translate member must either be NULL or a malloced pointer. (See http://sourceware.org/bugzilla/show_bug.cgi?id=5718) 3. It adds not_bol, not_eol and newline_anchor to the list of fields that are user-accessible after compilation (thanks to Bruno Haible for answering my question about this on bug-gnulib 29 Jul 10). Note that this patch only changes comments, not code. -- Summary: Missing documentation in regex.h Product: glibc Version: unspecified Status: NEW Severity: minor Priority: P2 Component: regex AssignedTo: drepper at redhat dot com ReportedBy: rrt at sc3d dot org CC: glibc-bugs-regex at sources dot redhat dot com,glibc- bugs at sources dot redhat dot com http://sourceware.org/bugzilla/show_bug.cgi?id=11857 ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
next reply other threads:[~2010-07-30 9:15 UTC|newest] Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top 2010-07-30 9:15 rrt at sc3d dot org [this message] 2010-07-30 9:29 ` [Bug regex/11857] " rrt at sc3d dot org 2010-07-30 19:30 ` rrt at sc3d dot org 2010-07-30 19:32 ` rrt at sc3d dot org 2010-07-30 20:20 ` rrt at sc3d dot org 2010-07-30 22:10 ` rrt at sc3d dot org 2010-07-31 19:34 ` rrt at sc3d dot org 2010-07-31 19:36 ` rrt at sc3d dot org
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=20100730091503.11857.rrt@sc3d.org \ --to=sourceware-bugzilla@sourceware.org \ --cc=glibc-bugs-regex@sources.redhat.com \ /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: linkBe 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).