This is the mail archive of the
guile@sourceware.cygnus.com
mailing list for the Guile project.
Re: Names in libguile
- To: ttn at glug dot org
- Subject: Re: Names in libguile
- From: Mikael Djurfeldt <mdj at mdj dot nada dot kth dot se>
- Date: 16 Mar 2000 22:59:09 +0100
- Cc: djurfeldt at nada dot kth dot se, guile at sourceware dot cygnus dot com
- Cc: djurfeldt at nada dot kth dot se
- References: <E12VeE6-0004Sb-00@mdj.nada.kth.se> <200003162129.NAA16749@revel.glug.org>
thi <ttn@revel.glug.org> writes:
> From: Mikael Djurfeldt <mdj@mdj.nada.kth.se>
> Date: Thu, 16 Mar 2000 18:38:26 +0100
>
> If there's a C variant of something provided at the Scheme level
> (like the current scm_internal_dynamic_wind), it has the prefix
> scm_c_ instead of scm_.
>
> this is the only one i don't understand. why is it important to
> reflect the origin of the definition?
By rule, the C level name of the Scheme primitive `dynamic-wind' is
scm_dynamic_wind.
However, we also need a suitable C level interface to this
functionality.
Since scm_dynamic_wind is occupied by the primitive (which is not easy
to use in C code), the C level version gets the name
scm_c_dynamic_wind.
We could extend this policy to say that *any* libguile function which
is not a primitive should have prefix scm_c_ ...