From: ludo@gnu.org (Ludovic Courtès)
To: guile-user@gnu.org
Subject: Re: A [serious] problem with module integration
Date: Fri, 16 Nov 2012 21:40:08 +0100 [thread overview]
Message-ID: <87vcd5wac7.fsf@gnu.org> (raw)
In-Reply-To: CAMFYt2YdPm2g47+OgXxDXDqOzgCPYrPjpWjJUt8rFmN5EOsaBw@mail.gmail.com
Hi!
Panicz Maciej Godek <godek.maciek@gmail.com> skribis:
> If I'd taken a different approach, e.g. if I'd decided to use shared
> libraries instead of having the main application call scm_with_guile,
> the solution would be easy -- I could just define the wrappers around
> the procedures exported by the library.
Yes. This is called /extending/ Guile, as opposed to /embedding/ it,
and it’s always more fruitful. See, for instance, the discussion at
<http://twistedmatrix.com/users/glyph/rant/extendit.html>.
Thanks,
Ludo’.
next prev parent reply other threads:[~2012-11-16 20:40 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-16 13:54 A [serious] problem with module integration Panicz Maciej Godek
2012-11-16 16:03 ` Mike Gran
2012-11-16 16:10 ` Mike Gran
2012-11-16 16:38 ` Panicz Maciej Godek
2012-11-16 16:41 ` Mark H Weaver
2012-11-16 17:10 ` Mike Gran
2012-11-16 20:40 ` Ludovic Courtès [this message]
2012-11-17 20:28 ` rixed
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=87vcd5wac7.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=guile-user@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).