This is the mail archive of the
guile@sourceware.cygnus.com
mailing list for the Guile project.
Re: modules names, locations, and how to register.
- To: "Marius Vollmer" <mvo at zagadka dot ping dot de>
- Subject: Re: modules names, locations, and how to register.
- From: "Marisha Ray & Neil Jerram" <mpriz at dircon dot co dot uk>
- Date: Sun, 10 Oct 1999 22:33:56 +0100
- Cc: <guile at sourceware dot cygnus dot com>, "James Dean Palmer" <james at tiger-marmalade dot com>
Marius Vollmer <mvo@zagadka.ping.de> writes
>;; - Write a function with a name like
>;;
>;; scm_init_ice_9_gtcltk_module
>;;
>;; This is your `module init' function. It should call
>;;
>;; scm_register_module_xxx ("ice-9 gtcltk", scm_init_gtcltk);
>;;
>;; "ice-9 gtcltk" is the C version of the module name. Slashes are
>;; replaced by spaces, the rest is untouched. `scm_init_gtcltk' is
>;; the real init function that executes the usual initializations
>;; like making new smobs, etc.
And, presumably, add a call to scm_init_ice_9_gtcltk_module() to somewhere
in the core of libguile?
>;; - Then you can simply write `:use-module (ice-9 gtcltk)' and it
>;; will be linked automatically.
Or is the call to scm_init_ice_9_gtcltk_module() automatically constructed
by `:use-module (ice-9 gtcltk)' if necessary?
Thanks,
Neil