From: Ivan Gyurdiev <ivg2@cornell.edu>
To: Ivan Gyurdiev <ivg2@cornell.edu>
Cc: selinux@tycho.nsa.gov, Stephen Smalley <sds@tycho.nsa.gov>
Subject: Re: [ SEPOL ] Context interface cleanup
Date: Fri, 21 Oct 2005 16:50:05 -0400 [thread overview]
Message-ID: <4359547D.3050001@cornell.edu> (raw)
In-Reply-To: <43595049.2@cornell.edu>
> - removes the sepol_ prefix, which I use to indicate whether a
> function is exported or not
Actually, can that still create a namespace conflict during static linking?
Would it make a difference if it was marked 'static' ?
What should I name all those things...
I want sepol_context_* to be reserved for the record that represents a
context..
I wanted context_* for the internal structure, for consistency with
other code (but the other code is static_inline...).
--
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:[~2005-10-21 20:50 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-10-21 20:32 [ SEPOL ] Context interface cleanup Ivan Gyurdiev
2005-10-21 20:50 ` Ivan Gyurdiev [this message]
2005-10-22 10:14 ` Ivan Gyurdiev
2005-10-24 12:47 ` Stephen Smalley
2005-10-24 14:47 ` Ivan Gyurdiev
2005-10-24 14:47 ` Stephen Smalley
2005-10-24 14:56 ` 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=4359547D.3050001@cornell.edu \
--to=ivg2@cornell.edu \
--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.