This is the mail archive of the guile@cygnus.com mailing list for the guile project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]

Re: The how and why of incorportating guile into an existingproject.


-----BEGIN PGP SIGNED MESSAGE-----

>and guile has had the necessary functions registered to emit text equivalent
>to the current autogen parser when it evaluates this expression...  is the C
>interface to guile documented well enough to find how to do this yet?
>
>That said, how are the primitives registered with guile?  Presumably a
>dynamically loaded shared library?  How does one build such a beast?
>
>Would you need to fire up a guile runtime to pass this stuff to, or would an
>embedded guile interpreter be linked in at compile time? presumably, the
>latter... is this documented?

I just recently started using Guile, and I found the new documentation
(with the dev. release) to be more than adequate for figuring out how to
interface C functions with Guile (depending upon how fancy you want to
get).  I recommend just diving in, and surfacing to ask questions if you
get stuck.

(Essentially, your program, linked with the libguile shared library, is
going to replace the guile executable for your users--there's no messing
around with dynamically-loaded plugins or anything like that.  Don't worry,
all of the functionality of the guile program is taken care of for you by a
single function, gh_repl; you only need to write your new primitives.  This
is all documented.)

Cordially,
Steven G. Johnson


-----BEGIN PGP SIGNATURE-----
Version: PGPfreeware 5.0 for non-commercial use <http://www.pgp.com>
Charset: noconv

iQEVAwUBNXeX/u3fOMhN2WfhAQGGyAf9H6A9tzpbi97gZ/7AdY7AnSxVJxgplasH
QPA++6oQtrE5FZ6/VOFjKknQQaLqghpGoxiRkCnJgcbIzHY7Yuw8QZnRUkWDwoZt
d5FXJZom+pLn8kVmniflBPnhLCs6rQI6qvLfs8FImJkbsoRTWOupoEbqRk0WExJp
j1gOyHOdODWsa0vPTuFY2dya5gfwVgZvkW9n+eqDH3cjFkL/+O6Do2b1lP0J7hFE
B5+ttJ1o43zsD9ym5f8xJB6ICjJibdj6pSA2JQCusGWDfQbJLFBovAuZANQ3uqCp
leFDKokL3AoSL4wUEyIL29eMyLrPHG/vq+nn94ZAyf0qIRwp9UDKMA==
=IkMq
-----END PGP SIGNATURE-----