unofficial mirror of bug-guile@gnu.org 
 help / color / mirror / Atom feed
From: Alexei Matveev <alexei.matveev@gmail.com>
To: 17869@debbugs.gnu.org
Subject: bug#17869: wrong return type for void scm_c_export(const char *name, ...) in docs
Date: Sun, 29 Jun 2014 13:55:13 +0200	[thread overview]
Message-ID: <CACMrLAc8=Ogw9aTQ8ng_qxdhY1KOROcvoxfMvRsVz_NEcu75tg@mail.gmail.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 1002 bytes --]

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

alexei@ThinkPad:~/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}.
 @end deftypefn

-@deftypefn {C Function} SCM scm_c_export ({const char *}@var{name}, ...)
+@deftypefn {C Function} void scm_c_export ({const char *}@var{name}, ...)
 Add the bindings designated by @var{name}, ... to the public interface
 of the current module.  The list of names is terminated by
 @code{NULL}.

[-- Attachment #2: Type: text/html, Size: 1965 bytes --]

             reply	other threads:[~2014-06-29 11:55 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-06-29 11:55 Alexei Matveev [this message]
2014-10-01 23:15 ` bug#17869: wrong return type for void scm_c_export(const char *name, ...) in docs Mark H Weaver

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='CACMrLAc8=Ogw9aTQ8ng_qxdhY1KOROcvoxfMvRsVz_NEcu75tg@mail.gmail.com' \
    --to=alexei.matveev@gmail.com \
    --cc=17869@debbugs.gnu.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).