unofficial mirror of guile-user@gnu.org 
 help / color / mirror / Atom feed
From: Brett Viren <bv@bnl.gov>
Cc: guile-user@gnu.org
Subject: Re: guile as extension language
Date: Sun, 7 Apr 2002 10:24:10 -0400	[thread overview]
Message-ID: <15536.22154.342488.354382@minos.phy.bnl.gov> (raw)
In-Reply-To: <200204062347.g36Nl7l21986@mr-ed.jpl.nasa.gov>

I am sure the experts will say more, but as a simple user I can say
that you can indeed embed (lib)guile into your executable w/out the
need to talk to the guile executable via sockets (ick!).

There are 2 ends of a spectrum in how you can embed guile.  On one
end, you can do everything in scheme and call scheme wrapped versions
of your library's functions.  On the other, you can do everything in
C/C++ and call into scheme either by passing strings of scheme code to
guile or via guile's scm_ C functions using "SCM" objects.

I have written both type of applications and both models are easy to
develop.  However, since dia's main loop is under GTK+'s control, you
will likely tend toward the former.

BTW, I think it would be way cool to extend dia with guile.  Do you
intend to use scheme as an output format instead of the current XML,
or just use it for run time extension, a'la emacs?

Regards,
-Brett.


_______________________________________________
Guile-user mailing list
Guile-user@gnu.org
http://mail.gnu.org/mailman/listinfo/guile-user


  parent reply	other threads:[~2002-04-07 14:24 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-04-06 23:47 guile as extension language Matthew R Wette
2002-04-07  3:29 ` 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 ` Brett Viren [this message]
2002-04-07 14:38 ` guile as extension language 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=15536.22154.342488.354382@minos.phy.bnl.gov \
    --to=bv@bnl.gov \
    --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).