From: Han-Wen Nienhuys <hanwen@cs.uu.nl>
Cc: guile-devel@gnu.org, jantien@xs4all.nl
Subject: Re: Modules: first steps.
Date: Thu, 19 Sep 2002 02:18:18 +0200 [thread overview]
Message-ID: <15753.6090.156090.648971@blauw.xs4all.nl> (raw)
In-Reply-To: <87ofavghdw.fsf@zagadka.ping.de>
mvo@zagadka.ping.de writes:
> > * It would be nice if the C smob example also touched on module use.
>
> There is "examples/box-module". Is that what you are looking for, or
> something else?
It would be nice if this was referred to in the documentation. I
accidentally stumbled upon it yesterday.
> > * I have in my code:
> The reason that you version didn't work is that when
> scm_c_resolve_module (and 'resolve-module') can't find the requested
> module, it returns a fresh, empty one. It is _totally_ empty, which
> means that things like 'use-modules' aren't available. Since you want
> to define a new module, you should use scm_c_define_module. It will
> do all the right things.
OK. The difference wasn't clear to me at all, and I don't think the
distinction is there in the doco.
This means that if I do
SCM mod = scm_c_define_module (...)
scm_set_current_module (mod)
scm_c_define ("foo", ... );
then 'foo is defined in MOD? This is what I really need.
--
Han-Wen Nienhuys | hanwen@cs.uu.nl | http://www.cs.uu.nl/~hanwen
_______________________________________________
Guile-devel mailing list
Guile-devel@gnu.org
http://mail.gnu.org/mailman/listinfo/guile-devel
next prev parent reply other threads:[~2002-09-19 0:18 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-09-15 23:42 Modules: first steps Han-Wen Nienhuys
2002-09-18 20:41 ` Marius Vollmer
2002-09-18 21:11 ` Tom Lord
2002-09-19 0:18 ` Han-Wen Nienhuys [this message]
2002-09-21 21:02 ` Marius Vollmer
2002-09-19 20:31 ` Han-Wen Nienhuys
2002-09-19 20:33 ` Rob Browning
2002-09-20 14:21 ` Martin Grabmueller
2002-09-20 22:40 ` Han-Wen Nienhuys
2002-09-19 20:38 ` Han-Wen Nienhuys
2002-09-21 21:07 ` Marius Vollmer
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=15753.6090.156090.648971@blauw.xs4all.nl \
--to=hanwen@cs.uu.nl \
--cc=guile-devel@gnu.org \
--cc=jantien@xs4all.nl \
/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).