[debbugs-tracker] bug#17869: closed (wrong return type for void scm_c_export(const char *name, ...) in docs)

[GNU bug Tracking System]

Your message dated Wed, 01 Oct 2014 19:15:06 -0400
with message-id <address@hidden>
and subject line Re: bug#17869: wrong return type for void scm_c_export(const 
char *name, ...) in docs
has caused the debbugs.gnu.org bug report #17869,
regarding wrong return type for void scm_c_export(const char *name, ...) in docs
to be marked as done.

(If you believe you have received this mail in error, please contact
address@hidden)


-- 
17869: http://debbugs.gnu.org/cgi/bugreport.cgi?bug=17869
GNU Bug Tracking System
Contact address@hidden with problems

--- Begin Message --- Subject: wrong return type for void scm_c_export(const char *name, ...) in docs Date: Sun, 29 Jun 2014 13:55:13 +0200

Dear Guile Developers,

The reference guide documents the wrong return type for

the vararg function

  void scm_c_export(const char *name, ...)

saying it is SCM. Consider applying the diff below.

Also, again vararg functions are troublesome (impossible)
to call from Fortran and, maybe other languages, please dont
let them proliferate in Guile API.

Alexei

address@hidden:~/devel/guile$ git diff
diff --git a/doc/ref/api-modules.texi b/doc/ref/api-modules.texi
index 286a37d..e2dc65f 100644
--- a/doc/ref/api-modules.texi
+++ b/doc/ref/api-modules.texi
@@ -1053,7 +1053,7 @@ module, as with @code{(use-modules @var{name})}.  The name is
 interpreted as for @code{scm_c_define_module}.
address@hidden deftypefn
 
address@hidden {C Function} SCM scm_c_export ({const char address@hidden, ...)
address@hidden {C Function} void scm_c_export ({const char address@hidden, ...)
 Add the bindings designated by @var{name}, ... to the public interface
 of the current module.  The list of names is terminated by
address@hidden

--- End Message ---

> --- Begin Message ---
>
>
>
> Subject: 
>
> Re: bug#17869: wrong return type for void scm_c_export(const char *name, ...) in docs
>
>
>
>
> Date: 
>
> Wed, 01 Oct 2014 19:15:06 -0400
>
>
>
>
> Fixed in b1451ad859183ae48c624d19ec144306bd2d3e3a on the stable-2.0
> branch.  It will be in 2.0.12.
>
>      Thanks!
>        Mark
>
>
> --- End Message ---