From: Andy <wangxinxi@cs.hit.edu.cn>
To: help-gnu-emacs@gnu.org
Subject: Re: How to use shared object in elisp?
Date: Mon, 16 Jul 2007 22:02:59 +0800 [thread overview]
Message-ID: <87ir8k1m5o.fsf@cs.hit.edu.cn> (raw)
In-Reply-To: 878x9gecsg.fsf@orme.bigwalter.net
Maybe I should write the program in Common Lisp and communicate
with emacs by socket.
daniel@bigwalter.net (Daniel Jensen) writes:
> Andy <wangxinxi@cs.hit.edu.cn> writes:
>
>> Can I use shared object in elisp? I have a libxxx.so written in C. And I
>> want to write a interface in elisp. What should I do?
>
> You'll have to write a wrapper program and call that from Emacs Lisp.
next prev parent reply other threads:[~2007-07-16 14:02 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-16 8:04 How to use shared object in elisp? Andy
2007-07-16 12:46 ` Daniel Jensen
2007-07-16 14:02 ` Andy [this message]
2007-07-16 14:34 ` Pascal Bourguignon
2007-07-17 7:37 ` Anselm Helbig
2007-07-17 11:16 ` Daniel Jensen
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=87ir8k1m5o.fsf@cs.hit.edu.cn \
--to=wangxinxi@cs.hit.edu.cn \
--cc=help-gnu-emacs@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.
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).