From: Ivan Gyurdiev <ivg2@cornell.edu>
To: Joshua Brindle <jbrindle@tresys.com>
Cc: SELinux List <SELinux@tycho.nsa.gov>,
Stephen Smalley <sds@tycho.nsa.gov>
Subject: Re: [SEMANAGE] Annotate objects
Date: Mon, 02 Jan 2006 12:08:45 -0500 [thread overview]
Message-ID: <43B95E1D.7020505@cornell.edu> (raw)
In-Reply-To: <43B975FB.8050106@tresys.com>
>> This patch adds comments that explain the object relationships, to
>> avoid confusion...
>>
>
> I don't think this avoids confusion at all. This isn't Java and C
> programmers aren't going to automatically understand Implements,
> Extends, etc.
Yes, the vocabulary draws from Java, because I have some Java background
- feel free to suggest something different, and I'll change the
comments. Implements -> interface (?) Extends -> inherits from (?)
--
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.
prev parent reply other threads:[~2006-01-02 17:08 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-12-23 6:34 [SEMANAGE] Annotate objects Ivan Gyurdiev
2006-01-02 18:50 ` Joshua Brindle
2006-01-02 17:08 ` Ivan Gyurdiev [this message]
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=43B95E1D.7020505@cornell.edu \
--to=ivg2@cornell.edu \
--cc=SELinux@tycho.nsa.gov \
--cc=jbrindle@tresys.com \
--cc=sds@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.