From: Christopher Cramer <crayc@pyro.net>
Cc: guile-devel@gnu.org
Subject: Re: scm_* API extension? [was] scm_* API question
Date: Wed, 31 Jul 2002 15:06:02 -0500 [thread overview]
Message-ID: <20020731150602.A32555@kiwi.pyrotechnics.com> (raw)
In-Reply-To: <ljeldkfbsk.fsf@burns.dt.e-technik.uni-dortmund.de>; from marius.vollmer@uni-dortmund.de on Wed, Jul 31, 2002 at 12:10:19PM +0200
On Wed, Jul 31, 2002 at 12:10:19PM +0200, Marius Vollmer wrote:
> rm@fabula.de writes:
>
> > Would it be usefull to provide a scm_* function for it?
>
> Yes. I will add this to CVS.
>
> However, I'd say it is better to code all module system manipulations
> in Scheme and try to keep the C code 'module system ignorant' if that
> is possible.
>
> Why do you want to perform module system operations from C? Maybe
> there is a more elegant way.
I have no idea why you think it would better, but with certain types of
applications, it's impossible.
For sake of argument, let's say there are two different ways to use Guile.
One way is to extend Guile through C, by using load-extension. This works
fine if the C code is ignorant of the module system (writing a wrapper
module in Scheme handles everything). The other way is to extend C through
Guile, which cannot stay module system ignorant, because you typically
want to load multiple Scheme scripts without worrying about clashing
symbols from the different scripts -- this is currently impossible
without getting deep into the details of the module system.
I can provide examples of what I had to do with Recluse; roughly 300 lines
of C code are devoted to dealing with the module system.
--
Christopher Cramer <crayc@pyro.net> <http://www.pyro.net/~crayc/>
On résiste à l'invasion des armées; on ne résiste pas à l'invasion
des idées. -- Victor Hugo
_______________________________________________
Guile-devel mailing list
Guile-devel@gnu.org
http://mail.gnu.org/mailman/listinfo/guile-devel
next prev parent reply other threads:[~2002-07-31 20:06 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-07-30 12:14 scm_* API question rm
2002-07-31 1:09 ` Christopher Cramer
2002-07-31 10:03 ` scm_* API extension? [was] " rm
2002-07-31 10:10 ` Marius Vollmer
2002-07-31 18:21 ` rm
2002-07-31 21:59 ` Rob Browning
2002-08-01 10:10 ` rm
2002-08-01 16:51 ` Rob Browning
2002-08-05 15:08 ` Marius Vollmer
2002-08-05 16:06 ` rm
2002-08-05 16:49 ` Marius Vollmer
2002-07-31 20:06 ` Christopher Cramer [this message]
2002-07-31 22:14 ` Rob Browning
2002-08-01 9:41 ` rm
2002-08-05 17:51 ` Marius Vollmer
2002-08-05 18:12 ` Han-Wen Nienhuys
2002-08-05 18:45 ` Rob Browning
2002-08-05 18:31 ` Rob Browning
2002-08-05 18:33 ` rm
2002-08-05 15:12 ` Marius Vollmer
2002-07-31 10:11 ` Marius Vollmer
2002-07-31 10:30 ` rm
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=20020731150602.A32555@kiwi.pyrotechnics.com \
--to=crayc@pyro.net \
--cc=guile-devel@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).