From: Christopher Cramer <crayc@pyro.net>
Cc: guile-devel@gnu.org
Subject: Re: scm_* API question
Date: Tue, 30 Jul 2002 20:09:29 -0500 [thread overview]
Message-ID: <20020730200929.A18106@kiwi.pyrotechnics.com> (raw)
In-Reply-To: <20020730121436.GA4465@www>; from rm@fabula.de on Tue, Jul 30, 2002 at 02:14:36PM +0200
On Tue, Jul 30, 2002 at 02:14:36PM +0200, rm@fabula.de wrote:
> in my application i have a SCM value that holds
> a list of symbols. I need to
>
> a) find the module that corresponds to this list,
> i.e. the scm_* counterpart of guile's resolve-module.
> Is:
>
> SCM my_list, my_module, my_symbol;
>
> ...
> my_module = scm_resolve_module(my_list);
>
> the right way?
Yes. Well, I think it might fail if the module isn't already loaded.
> b) access symbols from the module. Is:
>
> my_symbol = scm_module_lookup(my_module, a_symbol);
>
> ok?
Yes.
> c) use the module i found in step a. Hmm, the only thing i
> found so far is 'scm_c_use_module(char *)', but that takes
> a string (even without the enclosing brackets!) so i can't
> really use this (or do i have to build the string myself
> from my SCM list? Kind of silly, considering the fact that the
> list was built from a string using scm_c_read_string(char *).
Well, scm_c_use_module just calls process-use-modules, so you could
do that directly.
> Oh, btw, whad _does_ scm_c_read_string return if string isn't
> a valid S-expression?
It shouldn't return, but throw an exception with the misc-error key
and a helpful message.
--
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 1:09 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 [this message]
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
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=20020730200929.A18106@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).