From: Matthias Koeppe <mkoeppe@mail.Math.Uni-Magdeburg.De>
Cc: Rob Browning <rlb@defaultvalue.org>,
"Dale P. Smith" <dsmith@altustech.com>,
guile-devel@gnu.org
Subject: Re: What replaces scm_register_module_xxx (Doc update?)
Date: Fri, 09 Aug 2002 13:29:09 +0200 [thread overview]
Message-ID: <uw5lm7g6zju.fsf@saturn.math.uni-magdeburg.de> (raw)
In-Reply-To: <20020809100046.GB25104@www> (rm@fabula.de's message of "Fri, 9 Aug 2002 12:00:46 +0200")
rm@fabula.de writes:
> On Fri, Aug 09, 2002 at 10:47:50AM +0200, Matthias Koeppe wrote:
>> [...]
>>
>> He proposed and implemented a C API for defining modules and exporting
>> symbols, see
>>
>> http://mail.gnu.org/pipermail/guile-devel/2001-May/002171.html
>>
>> I use this API in the Guile back-end of SWIG (http://www.swig.org).
>> The functions are also mentioned in the NEWS file of Guile (changes
>> after release 1.4). The API is also used in
>> examples/box-module/box.c.
>
> Ah, thank's a lot, the "missing files". I remembered the discussion
> but forgot that Marius _did_ post a description of the new interface.
> Marius, just one more question: it looks like the signature of
> scm_c_define_module changed slightly since your mail back last may:
>
> scm_c_define_module (const char *name,
> void (*init)(void *), void *data)
>
> - what is the purpose of 'void *data' ?
It is an opaque argument...
> - what is passed to the init function in the void pointer and
> what is the function supposed to return?
... that is simply passed to the init function when it is invoked.
(This makes the init function a "C closure".) The init function
returns nothing (it has "void" return type).
>> I believe it's only an accident that the functions are not documented
>> (except for the NEWS blurb). I think documentation should be added;
>> the changes should also go into the 1.6 release. Preliminary
>> documentation can be found in the above message by Marius.
>
> Should this be documented soon?
Ralf, maybe you want to prepare a patch that adds the documentation to
Guile.
Regards,
--
Matthias Köppe -- http://www.math.uni-magdeburg.de/~mkoeppe
_______________________________________________
Guile-devel mailing list
Guile-devel@gnu.org
http://mail.gnu.org/mailman/listinfo/guile-devel
next prev parent reply other threads:[~2002-08-09 11:29 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-08-08 13:48 What replaces scm_register_module_xxx (Doc update?) rm
2002-08-08 14:21 ` Dale P. Smith
2002-08-08 14:23 ` Dale P. Smith
2002-08-08 14:31 ` Rob Browning
2002-08-08 16:19 ` rm
2002-08-08 17:59 ` Dale P. Smith
2002-08-08 18:24 ` rm
2002-08-08 20:26 ` Marius Vollmer
2002-08-08 21:28 ` Neil Jerram
2002-08-09 15:36 ` rm
2002-08-17 11:59 ` Neil Jerram
2002-08-19 19:05 ` rm
2002-08-09 8:47 ` Matthias Koeppe
2002-08-09 10:00 ` rm
2002-08-09 11:29 ` Matthias Koeppe [this message]
2002-08-09 13:23 ` rm
2002-08-10 14:44 ` Marius Vollmer
2002-08-11 23:20 ` Marius Vollmer
2002-08-17 8:09 ` Dirk Herrmann
2002-08-17 11:05 ` Neil Jerram
2002-08-24 8:08 ` Dirk Herrmann
2002-08-26 21:45 ` Neil Jerram
2002-08-26 22:04 ` Marius Vollmer
2002-08-21 19:35 ` Marius Vollmer
2002-08-13 0:40 ` Marius Vollmer
2002-08-17 22:37 ` Dale P. Smith
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=uw5lm7g6zju.fsf@saturn.math.uni-magdeburg.de \
--to=mkoeppe@mail.math.uni-magdeburg.de \
--cc=dsmith@altustech.com \
--cc=guile-devel@gnu.org \
--cc=rlb@defaultvalue.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).