From: Ivan Gyurdiev <ivg2@cornell.edu>
To: Kevin Carr <kcarr@tresys.com>
Cc: Stephen Smalley <sds@tycho.nsa.gov>,
selinux@tycho.nsa.gov, Selinux-Dev <selinux-dev@tresys.com>
Subject: Re: [RFC][PATCH] extending the libsepol API
Date: Mon, 27 Mar 2006 18:59:26 -0500 [thread overview]
Message-ID: <44287C5E.3030307@cornell.edu> (raw)
In-Reply-To: <200603212246.k2LMkRNq028071@gotham.columbia.tresys.com>
> the caller is
> + * responsible for safely casting this pointer.
Do you plan to iterate over opaque objects, such as the current record
implementations?
> + * errno will be set and *item will be NULL.
Elsewhere we use a callback to communicate an error condition with the
caller.
What's the advantage of errno over pre-defined return codes?
+extern int sepol_iterator_get_size(sepol_iterator_t *iter, size_t *size);
Shouldn't this be "unsigned int" instead?
--
This message was distributed to subscribers of the selinux mailing list.
If you no longer wish to subscribe, send mail to majordomo@tycho.nsa.gov with
the words "unsubscribe selinux" without quotes as the message.
next prev parent reply other threads:[~2006-03-27 23:59 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-21 22:46 [RFC][PATCH] extending the libsepol API Kevin Carr
2006-03-22 12:51 ` Stephen Smalley
2006-03-22 15:55 ` Kevin Carr
2006-03-28 0:53 ` Ivan Gyurdiev
2006-03-23 20:41 ` Stephen Smalley
2006-03-27 23:59 ` Ivan Gyurdiev [this message]
[not found] <1143123154.28120.300.camel@moss-spartans.epoch.ncsc.mil>
2006-03-23 19:23 ` Kevin Carr
2006-03-23 19:58 ` Stephen Smalley
2006-03-24 13:37 ` Stephen Smalley
2006-03-24 17:24 ` Kevin Carr
2006-03-28 0:27 ` Ivan Gyurdiev
2006-03-28 0:42 ` Ivan Gyurdiev
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=44287C5E.3030307@cornell.edu \
--to=ivg2@cornell.edu \
--cc=kcarr@tresys.com \
--cc=sds@tycho.nsa.gov \
--cc=selinux-dev@tresys.com \
--cc=selinux@tycho.nsa.gov \
/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.