From: Dmitry Bogatov <KAction@gnu.org>
To: guile-devel@gnu.org
Subject: Guile and Swig
Date: Wed, 17 Apr 2013 09:28:39 +0400 [thread overview]
Message-ID: <87li8hsp2w.fsf@gnu.org> (raw)
Hello, list!
Is using SWIG[1] is endorsed for writing Guile wrappers to C library? I
make such bindings for libircclient[2] for my project, but it would be
nice, if it would find way to official Guile tree. Are here some
guidelines about it?
Also, question of style of Lisp code. It seems, that most common style
is `(action object arg1 ...)` and I find making object callable is more
elegant: `(object #:action arg1 ...)`. Is it discouraged?
1. http://www.swig.org/
2. http://www.ulduzsoft.com/linux/libircclient/
--
Best regards, Dmitry Bogatov <KAction@gnu.org>,
Free Software supporter and netiquette guardian.
git://gitorious.org/illusionoflife-read-only/rc-files.git
GPG: 54B7F00D
Html mail and proprietary format attachments are forwarded to /dev/null.
next reply other threads:[~2013-04-17 5:28 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-17 5:28 Dmitry Bogatov [this message]
2013-04-19 0:06 ` Guile and Swig Daniel Hartwig
2013-04-19 6:15 ` Guile lisp code style (was: [guile] Re: Guile and Swig) Dmitry Bogatov
2013-04-19 7:46 ` Daniel Hartwig
2013-04-20 13:51 ` Guile and Swig Ludovic Courtès
2013-04-21 6:45 ` Ian Price
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/guile/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87li8hsp2w.fsf@gnu.org \
--to=kaction@gnu.org \
--cc=guile-devel@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).