From: Michael Kerrisk <mtk.manpages-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: Anthony Foiani <anthony.foiani-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Cc: linux-man-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: linux man pages: pthread_create(3): oddball comment
Date: Mon, 27 May 2013 04:49:05 +0200 [thread overview]
Message-ID: <51A2C9A1.8010609@gmail.com> (raw)
In-Reply-To: <CAOhNY-8fhrBTvvZdegz2oXxJ8J-6gc6vQVe3nXWtNnizQ4yRuQ-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
On 05/24/13 06:58, Anthony Foiani wrote:
> Greetings.
>
> The man page for pthread_create:
>
> http://man7.org/linux/man-pages/man3/pthread_create.3.html
>
> Has some example code at the bottom; one of the invocations includes
> this bit of commentary:
>
> 8192 # The stack size limit is 8 MB (0x80000 bytes)
>
> I had to stare at that a bit; I believe it should actually be 0x800000
> (note 5 zeros, not 4).
Yes, of course you are right! I'll fix. Thanks for reporting the problem.
> (I do wish that we -- the computing community -- had managed to come
> up with a sane digits separator for hex, but oh well. 0x80_0000
> maybe? 0x80'0000? just 0x80,0000?)
Actually, D get's this right -- it allows free use of underscores
in numeric literals.
Cheers,
Michael
--
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
next prev parent reply other threads:[~2013-05-27 2:49 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-24 4:58 linux man pages: pthread_create(3): oddball comment Anthony Foiani
[not found] ` <CAOhNY-8fhrBTvvZdegz2oXxJ8J-6gc6vQVe3nXWtNnizQ4yRuQ-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2013-05-27 2:49 ` Michael Kerrisk [this message]
[not found] ` <51A2C9A1.8010609-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2013-06-03 14:56 ` Anthony Foiani
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=51A2C9A1.8010609@gmail.com \
--to=mtk.manpages-re5jqeeqqe8avxtiumwx3w@public.gmane.org \
--cc=anthony.foiani-Re5JQEeQqe8AvxtiuMwx3w@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 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).