All of lore.kernel.org
 help / color / mirror / Atom feed
From: Joshua Brindle <jbrindle@tresys.com>
To: Ivan Gyurdiev <ivg2@cornell.edu>
Cc: Stephen Smalley <sds@tycho.nsa.gov>,
	Daniel J Walsh <dwalsh@redhat.com>,
	SELinux <SELinux@tycho.nsa.gov>
Subject: Re: [PATCH] Add seuser and user_extra to package format
Date: Tue, 07 Feb 2006 16:23:55 -0500	[thread overview]
Message-ID: <43E90FEB.6010503@tresys.com> (raw)
In-Reply-To: <43E8FD98.20202@cornell.edu>

Ivan Gyurdiev wrote:
> 
>>
>> IMO we should leave the semanageswig.i as the language neutral 
>> interface file (and not remove the _by_idx functions) and make 
>> language specific files include it. Then all the common parts are in 
>> semanageswig.i and python specific ones are in another file. That way 
>> we are free to use better features for python without eliminating the 
>> possibility of building the wrappers for another language and it 
>> shouldn't make maintenance any harder.
> Have you tried to see if the current typemaps work on any other language?
> I don't think the t_output_helper function you're using is defined in 
> any other language except for python.
> 

Ok, it looks like you are right, I just tried it on perl and 
t_output_helper was undefined. So aside from the #includes and the 
*_by_idx pretty much everything in the current .i file is python specific.

It looks like this library is sufficiently complex that there will need 
to be a .i file for each language supported, unfortunately.

We can still use the semanageswig.i to pull in all the headers that we 
are wrapping and put language specific things in their own .i file.

--
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.

      reply	other threads:[~2006-02-07 21:23 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-02-06 22:39 [PATCH] Add seuser and user_extra to package format Joshua Brindle
2006-02-07  3:04 ` Ivan Gyurdiev
2006-02-07  3:10   ` Joshua Brindle
2006-02-07 14:34   ` Stephen Smalley
2006-02-07 14:59     ` Ivan Gyurdiev
2006-02-07 15:20       ` Daniel J Walsh
2006-02-07 17:52     ` Joshua Brindle
2006-02-07 18:15       ` Daniel J Walsh
2006-02-07 20:05       ` Ivan Gyurdiev
2006-02-07 21:23         ` Joshua Brindle [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=43E90FEB.6010503@tresys.com \
    --to=jbrindle@tresys.com \
    --cc=SELinux@tycho.nsa.gov \
    --cc=dwalsh@redhat.com \
    --cc=ivg2@cornell.edu \
    --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.