From: Matthew R Wette <mwette@grover.jpl.nasa.gov>
Subject: Re: guile as extension language
Date: Sat, 06 Apr 2002 15:47:07 -0800 [thread overview]
Message-ID: <200204062347.g36Nl7l21986@mr-ed.jpl.nasa.gov> (raw)
Matthew R Wette writes ...
>
> How is Guile intended to be used as an extension language?
>
> Some extension languages like Perl can be fed commands from the main
> application. I believe the Apache Perl module works this way.
>
> Other extension languages can not be run this way and need to execute
> in a separate process, typically communicating via a socket
> connection. I believe the Apache Java servlet modules work this way.
>
> I just read through the Guile 1.5.6 code and it seems that Guile
> cannot be fed commands from a parent application like the first case
> above. If you want to use Guile as an *extension* language you need
> to run it in a separate process and talk via sockets. For example, if
> I wanted to generate a Guile Apache module it seems I would need to do
> it this way. Is this correct?
By the way, I noticed that The GIMP uses a separate process
to run script-fu.
My interest here was in exploring the scope of work required to
make a Guile extension for Dia (the gnome graphics app).
Matt
_______________________________________________
Guile-user mailing list
Guile-user@gnu.org
http://mail.gnu.org/mailman/listinfo/guile-user
next reply other threads:[~2002-04-06 23:47 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-04-06 23:47 Matthew R Wette [this message]
2002-04-07 3:29 ` guile as extension language Paul Emsley
2002-04-07 14:38 ` Neil Jerram
2002-04-08 11:43 ` Bill Schottstaedt
2002-04-16 8:17 ` HELP: crash while using Guile on a Win32 multithreaded development context Daniel CAUNE
2002-04-07 14:24 ` guile as extension language Brett Viren
2002-04-07 14:38 ` Neil Jerram
-- strict thread matches above, loose matches on Subject: below --
2002-04-06 23:33 Matthew R Wette
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=200204062347.g36Nl7l21986@mr-ed.jpl.nasa.gov \
--to=mwette@grover.jpl.nasa.gov \
/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).