From: Joshua Brindle <method@manicmethod.com>
To: Karl MacMillan <kmacmillan@mentalrootkit.com>
Cc: Brian Pomerantz <bapper@piratehaven.org>, selinux@tycho.nsa.gov
Subject: Re: [PATCH] Basic policy representation
Date: Fri, 11 May 2007 11:27:29 -0400 [thread overview]
Message-ID: <46448B61.9080808@manicmethod.com> (raw)
In-Reply-To: <1178719410.2379.32.camel@localhost.localdomain>
Karl MacMillan wrote:
> On Tue, 2007-05-08 at 15:41 -0400, Karl MacMillan wrote:
>
>> I actually prefer returning char instead - to me that is a common way to
>> indicate that the returned value has a limited range of values (2 in
>> this case). But maybe that is just the code bases I've worked on. I
>> don't care either way - this seems like a bike shed discussion . . .
>>
>>
>
> On the other hand, the existing code (for things like sepol_bool) uses
> int for boolean values. So I'll change to using int everywhere.
> Ahh . . . the bike shed looks much nicer painted blue rather than green.
>
Not to drag this mostly irrelevant discussion out longer but the setools
guys have decided to move to using stdbool.h and proper bool types for
all their boolean functions, is there a reason we can't do that? I was
surprised to find out that setting a bool value to anything other than 0
would cause it to be 1, so it really behaves like a boolean (strange..
I'm not use to C doing things the way you'd expect them to :P )
Also the bikeshed should be red.
--
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:[~2007-05-11 15:28 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-07 22:06 [PATCH] Basic policy representation Karl MacMillan
2007-05-08 14:45 ` Joshua Brindle
2007-05-08 15:08 ` Karl MacMillan
2007-05-08 15:48 ` Joshua Brindle
2007-05-08 16:11 ` Karl MacMillan
2007-05-08 16:47 ` Brian Pomerantz
2007-05-08 19:41 ` Karl MacMillan
2007-05-09 14:03 ` Karl MacMillan
2007-05-11 15:27 ` Joshua Brindle [this message]
2007-05-11 18:45 ` Karl MacMillan
2007-05-08 17:13 ` Stephen Smalley
2007-05-08 18:37 ` Joshua Brindle
2007-05-08 19:05 ` Stephen Smalley
2007-05-08 19:28 ` Joshua Brindle
2007-05-08 19:36 ` Karl MacMillan
2007-05-08 16:50 ` Stephen Smalley
2007-05-09 16:24 ` James Antill
2007-05-09 18:31 ` Karl MacMillan
2007-05-09 18:35 ` J. Tang
2007-05-09 19:22 ` Karl MacMillan
2007-05-09 22:46 ` J. Tang
2007-05-09 23:26 ` Karl MacMillan
2007-05-10 19:42 ` J. Tang
2007-05-10 20:00 ` Karl MacMillan
-- strict thread matches above, loose matches on Subject: below --
2007-05-10 17:56 Karl MacMillan
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=46448B61.9080808@manicmethod.com \
--to=method@manicmethod.com \
--cc=bapper@piratehaven.org \
--cc=kmacmillan@mentalrootkit.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.