c interface to modules

c interface to modules

[Ondrej Zajicek]

Hello
I would like to export two sets (low-level and high-level interface)
of C functions to Scheme. I think it is a good idea to have each
interface in different module. What is a good way to define C
function in specific module? Should i just replace scm_c_define_gsubr
with combination of scm_c_make_gsubr and scm_c_module_define?

-- 
Elen sila lumenn' omentielvo

Ondrej 'SanTiago' Zajicek (email: santiago@mail.cz, jabber: santiago@njs.netlab.cz)
OpenPGP encrypted e-mails preferred (KeyID 0x11DEADC3, wwwkeys.pgp.net)
"To err is human -- to blame it on a computer is even more so."


_______________________________________________
Guile-user mailing list
Guile-user@gnu.org
http://lists.gnu.org/mailman/listinfo/guile-user

Re: c interface to modules

[Rob Browning]

Ondrej Zajicek <santiago@mail.cz> writes:

> I would like to export two sets (low-level and high-level interface)
> of C functions to Scheme. I think it is a good idea to have each
> interface in different module. What is a good way to define C
> function in specific module? Should i just replace
> scm_c_define_gsubr with combination of scm_c_make_gsubr and
> scm_c_module_define?

If you write each of your modules as a .scm file which loads a C
library and calls an init function (see 1.6's srfi-13.scm, for
example), then you can just have two init functions in your C library,
one for the low-level functions, and one for the high-level functions,
i.e.

  ;; high-level.scm
  (define-module (high-level))
  (load-extension "libguile-foo-v-1" "scm_init_foo_high_level")
  (export bar)
  ...


  ;; high-level.scm
  (define-module (low-level))
  (load-extension "libguile-foo-v-1" "scm_init_foo_low_level")
  (export baz)
  ...

-- 
Rob Browning
rlb @defaultvalue.org and @debian.org; previously @cs.utexas.edu
GPG starting 2002-11-03 = 14DD 432F AE39 534D B592  F9A0 25C8 D377 8C7E 73A4


_______________________________________________
Guile-user mailing list
Guile-user@gnu.org
http://lists.gnu.org/mailman/listinfo/guile-user

Re: c interface to modules

[Jonathan Wilson]

Whoops! I always forget and just hit reply, then the message doesn't go 
to the list.

Ondrej Zajicek wrote:

>Hello
>I would like to export two sets (low-level and high-level interface)
>of C functions to Scheme. I think it is a good idea to have each
>interface in different module. What is a good way to define C
>function in specific module? Should i just replace scm_c_define_gsubr
>with combination of scm_c_make_gsubr and scm_c_module_define?
>
>  
>
Hi Ondrej!
I would use SWIG if I were you.  Very simple, fast, and easy.  Does all
the drudge work of creating wrapper functions and all for you.
http://www.swig.org/  I have not used it for anything large scale, but
the smaller scale stuff I have done to test it out worked like a charm!
It will create a xxx_wrap.c file for every xxx.c or xxx.h file you feed
it, then you compile these wrapper files and link them into a shared
library along with the original code (and whatever libraries it needs to
link with).  Then you can either just use (load-extension "xxx.so"
"SWIG_init") directly, or write a module in Scheme that loads the shared
lib whenever the module is loaded.

Best of luck!
Jon




_______________________________________________
Guile-user mailing list
Guile-user@gnu.org
http://lists.gnu.org/mailman/listinfo/guile-user