From: Daniel Hartwig <mandyke@gmail.com>
To: Dmitry Bogatov <KAction@gnu.org>
Cc: guile-devel@gnu.org
Subject: Re: Guile and Swig
Date: Fri, 19 Apr 2013 08:06:38 +0800 [thread overview]
Message-ID: <CAN3veRdBmfMBbTB3ewE7pE2sbT0q+v7q2fZd3JJajRRZt1wwiw@mail.gmail.com> (raw)
In-Reply-To: <87li8hsp2w.fsf@gnu.org>
On 17 April 2013 13:28, Dmitry Bogatov <KAction@gnu.org> wrote:
>
> Hello, list!
>
Hello now
> 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?
>
The guile support in swig is under maintained at best. It may not
even work correctly for guile-2.0.
> 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?
On some level both styles are functionally equivalent, although
conceptually they are quite different. It is more or less a matter of
taste. However, certain tasks are easier in one style or the other.
Why do you find the second style more elegant?
next prev parent reply other threads:[~2013-04-19 0:06 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-17 5:28 Guile and Swig Dmitry Bogatov
2013-04-19 0:06 ` Daniel Hartwig [this message]
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=CAN3veRdBmfMBbTB3ewE7pE2sbT0q+v7q2fZd3JJajRRZt1wwiw@mail.gmail.com \
--to=mandyke@gmail.com \
--cc=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).