From: "Kjetil S. Matheussen" <k.s.matheussen@notam02.no>
To: Neil Jerram <neiljerram@googlemail.com>
Cc: guile-user@gnu.org, "Kjetil S. Matheussen" <k.s.matheussen@notam02.no>
Subject: Re: Killing off scm_init_guile for Guile 2.0 ?
Date: Fri, 23 Jan 2009 10:12:51 +0100 (CET) [thread overview]
Message-ID: <Pine.LNX.4.64-L.0901231012090.23317@anakin.ifi.uio.no> (raw)
In-Reply-To: <49dd78620901221744k104bafe7h844d050d6a8e6cc7@mail.gmail.com>
On Fri, 23 Jan 2009, Neil Jerram wrote:
> 2009/1/16 Kjetil S. Matheussen <k.s.matheussen@notam02.no>:
>>
>> Snd uses scm_init_guile when compiled as a Pd external.
>> Pd is a graphical programming language for audio processing,
>> and "externals" are linked into the program during runtime.
>>
>> When Snd is a Pd external, it has to run Guile in a separate
>> thread, so that it won't interrupt sound processing.
>>
>> Is there an alternative to using scm_init_guile() for this
>> kind of usage?
>
> Yes: just use scm_with_guile() at all the entry points into
> libguile-land. Would that be possible?
>
Yes, that seems to work just fine. Thanks!
next prev parent reply other threads:[~2009-01-23 9:12 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <cmu-lmtpd-4567-1232125596-3@mail-imap1.uio.no>
2009-01-16 17:20 ` Killing off scm_init_guile for Guile 2.0 ? Kjetil S. Matheussen
2009-01-23 1:44 ` Neil Jerram
2009-01-23 9:12 ` Kjetil S. Matheussen [this message]
2009-01-15 23:30 Neil Jerram
2009-01-15 23:48 ` Neil Jerram
2009-01-16 14:57 ` Ludovic Courtès
2009-01-16 3:59 ` Linas Vepstas
2009-01-16 15:00 ` Ludovic Courtès
2009-01-16 15:41 ` Bill Schottstaedt
2009-01-23 1:49 ` Neil Jerram
2009-01-16 21:32 ` dsmich
2009-01-17 1:36 ` Linas Vepstas
2009-01-21 21:52 ` Zeeshan Ali (Khattak)
2009-01-23 2:02 ` Neil Jerram
2009-01-23 6:13 ` Clinton Ebadi
2009-01-23 16:23 ` Ludovic Courtès
2009-01-23 16:21 ` Ludovic Courtès
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=Pine.LNX.4.64-L.0901231012090.23317@anakin.ifi.uio.no \
--to=k.s.matheussen@notam02.no \
--cc=guile-user@gnu.org \
--cc=neiljerram@googlemail.com \
/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).