unofficial mirror of guile-devel@gnu.org 
 help / color / mirror / Atom feed
From: prj@po.cwru.edu (Paul Jarc)
Subject: Re: setgroups
Date: Fri, 18 Apr 2003 12:00:40 -0400	[thread overview]
Message-ID: <m3istbu75t.fsf@multivac.cwru.edu> (raw)
In-Reply-To: <87vfxb3jac.fsf@raven.i.defaultvalue.org> (Rob Browning's message of "Fri, 18 Apr 2003 10:41:15 -0500")

Rob Browning <rlb@defaultvalue.org> wrote:
> If there's nothing like GID_MAX, I guess we'll need to compute the
> fit manually.

unsigned long lgid = SCM_INUM (foo);
GETGROUPS_T gid = lgid;
if (gid < 0 || lgid != (unsigned long) gid) overflow;

- Is SCM_INUM guaranteed to fit in unsigned long?  If not, what type
  can we use instead?
- If GETGROUPS_T is signed and "gid = lgid" overflows, the C standard
  says it's undefined behavior.  Are we worried about that, or are we
  confident that it'll just wrap on platforms we care about?


paul


_______________________________________________
Guile-devel mailing list
Guile-devel@gnu.org
http://mail.gnu.org/mailman/listinfo/guile-devel


  reply	other threads:[~2003-04-18 16:00 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <m3y928ripu.fsf@multivac.cwru.edu>
2003-04-17 22:29 ` setgroups Rob Browning
2003-04-17 22:43   ` setgroups Paul Jarc
2003-04-17 23:10     ` setgroups Marius Vollmer
2003-04-18  3:19     ` setgroups Rob Browning
2003-04-17 23:20   ` setgroups Paul Jarc
2003-04-18  3:34     ` setgroups Rob Browning
2003-04-18 10:31       ` setgroups Marius Vollmer
2003-04-18 15:37         ` setgroups Paul Jarc
2003-04-18 17:38           ` setgroups Paul Jarc
2003-04-18 17:49             ` setgroups Paul Jarc
2003-04-21 16:20               ` setgroups Paul Jarc
2003-04-18 15:41         ` setgroups Rob Browning
2003-04-18 16:00           ` Paul Jarc [this message]
2003-04-18 17:01             ` setgroups Rob Browning

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

  List information: https://www.gnu.org/software/guile/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=m3istbu75t.fsf@multivac.cwru.edu \
    --to=prj@po.cwru.edu \
    /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).