From: "George Spelvin" <linux@horizon.com>
To: git@vger.kernel.org
Cc: sn_@gmx.net, linux@horizon.com
Subject: Re: [PATCH v2] Improve portability: Cast pid_t's to intmax_t
Date: Mon, 01 Sep 2008 04:28:01 -0400 [thread overview]
Message-ID: <20080901082801.29621.qmail@science.horizon.com> (raw)
This seems rather pointless. Whatever Solaris thinks, I really doubt
that process IDs will ever overflow an int, which is 32 bits on all
machines that will ever support more than 32k processes.
You can be paranoid if you like and cast to long, but I don't think
even a massive 64-bit cluster is likely to have more than 2G processes
in the forseeable future.
I'd support a cast to int or unsigned, or a cast to long as a second choice.
Using uintmax_t is formally correct, but practically pointless clutter.
next reply other threads:[~2008-09-01 8:35 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-01 8:28 George Spelvin [this message]
2008-09-01 8:54 ` [PATCH v2] Improve portability: Cast pid_t's to intmax_t Miles Bader
-- strict thread matches above, loose matches on Subject: below --
2008-08-31 12:09 David Soria Parra
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=20080901082801.29621.qmail@science.horizon.com \
--to=linux@horizon.com \
--cc=git@vger.kernel.org \
--cc=sn_@gmx.net \
/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).