All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Michael Kerrisk (man-pages)" <mtk.manpages-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: Laurence Gonsalves <laurence-IXX7sqgBUuUXtBFVwdE/iw@public.gmane.org>
Cc: mtk.manpages-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org,
	linux-man-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: Possibly misleading description of cflags parameter in regcomp(3)
Date: Wed, 06 May 2015 13:13:17 +0200	[thread overview]
Message-ID: <5549F74D.6050504@gmail.com> (raw)
In-Reply-To: <CAJbtQC8O8D+MJvFehX7N_t7ewaOxwhH9ttJr_uQ9RA3mQC2MrA-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>

Laurence,

On 09/22/2013 08:41 PM, Laurence Gonsalves wrote:
> Hello.
> 
> "man 3 regcomp" says "cflags may be the bitwise-or of one or more of
> the following", but I'm fairly certain that 0 is also a legal value
> for this parameter.
> 
> The page http://pubs.opengroup.org/onlinepubs/009695399/functions/regcomp.html
> says "The cflags argument is the bitwise-inclusive OR of zero or more
> of the following flags...".
> 
> If 0 is, indeed, a legal value then I think it would be more clear if
> the manpage said "cflags may be the bitwise-or of zero or more of the
> following".
> 
> (Sorry for the duplicate email. vger.kernel.org bounced the original
> apparently due to Gmail's use of HTML.)

Quite some time after your report...

I agree, and I've made the change.

Cheers,

Michael






-- 
Michael Kerrisk
Linux man-pages maintainer; http://www.kernel.org/doc/man-pages/
Linux/UNIX System Programming Training: http://man7.org/training/
--
To unsubscribe from this list: send the line "unsubscribe linux-man" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

      parent reply	other threads:[~2015-05-06 11:13 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-09-22 18:41 Possibly misleading description of cflags parameter in regcomp(3) Laurence Gonsalves
     [not found] ` <CAJbtQC8O8D+MJvFehX7N_t7ewaOxwhH9ttJr_uQ9RA3mQC2MrA-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2015-05-06 11:13   ` 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=5549F74D.6050504@gmail.com \
    --to=mtk.manpages-re5jqeeqqe8avxtiumwx3w@public.gmane.org \
    --cc=laurence-IXX7sqgBUuUXtBFVwdE/iw@public.gmane.org \
    --cc=linux-man-u79uwXL29TY76Z2rM5mHXA@public.gmane.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.