From: joakim@verona.se
To: rms@gnu.org
Cc: jtk@yahoo.com, phil@hagelb.org, monnier@iro.umontreal.ca,
emacs-devel@gnu.org
Subject: Re: obby
Date: Wed, 13 May 2009 11:53:44 +0200 [thread overview]
Message-ID: <m3zldh1g7r.fsf@verona.se> (raw)
In-Reply-To: <E1M4AWi-0005DE-B3@fencepost.gnu.org> (Richard M. Stallman's message of "Wed, 13 May 2009 05:13:24 -0400")
Richard M Stallman <rms@gnu.org> writes:
> Another aproach I was thinking of was writing some kind of plugin for
> the Swig wrapper generator for elisp. The idea is that Swig would be
> persuaded to generate C stubs and low-level elisp api:s from a C library
> .h file, like Swig already does for Java, Python and so on. I think this
> aproach would both be fairly convenient(not as convenient as dynamic
> linking of course) and safe from potential threats from dynamic linking.
>
> I can see how generating wrappers could be useful, but how could it help
> deal with the potential threat of non-free add-ons?
The wrappers would be statically linked. This would be the same
situation we have today, that is, elisp on top of statically linked
wrappers for dynamic libraries, for instance librsvg.
I should note that I dont fully understand why the GPL cant be relied on
to prevent linking to non-free dynamic libraries, so my analysis might
be flawed.
>
--
Joakim Verona
next prev parent reply other threads:[~2009-05-13 9:53 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-10 19:53 obby Richard M Stallman
2009-05-10 21:29 ` obby Jeff Kowalczyk
2009-05-11 14:35 ` obby Jeff Kowalczyk
2009-05-11 16:25 ` obby Phil Hagelberg
2009-05-11 17:19 ` obby Stefan Monnier
2009-05-11 18:25 ` obby joakim
2009-05-13 9:13 ` obby Richard M Stallman
2009-05-13 9:53 ` joakim [this message]
2009-05-13 22:34 ` obby Richard M Stallman
2009-05-21 18:35 ` obby Richard M Stallman
2009-05-22 11:41 ` obby Christian Lynbech
2009-05-22 16:45 ` obby Phil Hagelberg
2009-05-23 15:38 ` obby Richard M Stallman
2009-05-22 16:42 ` obby Phil Hagelberg
2009-05-23 14:32 ` obby Karl Fogel
2009-05-25 1:11 ` obby Stefan Monnier
2009-05-25 14:45 ` obby Karl Fogel
2009-05-25 15:02 ` obby Stefan Monnier
2009-05-23 15:38 ` obby Richard M Stallman
2009-05-11 21:08 ` obby Richard M Stallman
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=m3zldh1g7r.fsf@verona.se \
--to=joakim@verona.se \
--cc=emacs-devel@gnu.org \
--cc=jtk@yahoo.com \
--cc=monnier@iro.umontreal.ca \
--cc=phil@hagelb.org \
--cc=rms@gnu.org \
/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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).