From: Ivan Gyurdiev <ivg2@cornell.edu>
To: Kevin Carr <kcarr@tresys.com>
Cc: sds@tycho.nsa.gov, selinux@tycho.nsa.gov, SELinux-dev@tresys.com
Subject: Re: [RFC][PATCH] extending the libsepol API
Date: Mon, 27 Mar 2006 19:42:34 -0500 [thread overview]
Message-ID: <4428867A.8040904@cornell.edu> (raw)
In-Reply-To: <200603231923.k2NJNMNq014574@gotham.columbia.tresys.com>
>>> Also iterators can be used consistently across the
>>> entire API and every usage is the same as far as the user is concerned.
>>>
So, that's essentially an "Iterable" interface that you want to create,
which is implemented by all records.
I like OOP ideas, and inheritance/interfaces... otoh I don't like void*
and casting from it.
I think OOP ideas help when you want to put multiple object types in the
same framework - is this necessary here?
I don't think it increases readability otherwise.
By the way, this argument extends to the dbase interface in libsemanage.
--
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-28 0:42 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1143123154.28120.300.camel@moss-spartans.epoch.ncsc.mil>
2006-03-23 19:23 ` [RFC][PATCH] extending the libsepol API 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 [this message]
2006-03-21 22:46 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
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=4428867A.8040904@cornell.edu \
--to=ivg2@cornell.edu \
--cc=SELinux-dev@tresys.com \
--cc=kcarr@tresys.com \
--cc=sds@tycho.nsa.gov \
--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.