From: "Ludovic Courtès" <INVALID.NOREPLY@gnu.org>
To: "Ludovic Courtès" <ludo@gnu.org>, bug-guile@gnu.org
Subject: [bug #23681] Function declarators with empty parentheses should not be used
Date: Mon, 23 Jun 2008 11:45:46 +0000 [thread overview]
Message-ID: <20080623-114546.sv15145.2251@savannah.gnu.org> (raw)
In-Reply-To:
URL:
<http://savannah.gnu.org/bugs/?23681>
Summary: Function declarators with empty parentheses should
not be used
Project: Guile
Submitted by: civodul
Submitted on: Monday 06/23/2008 at 11:45
Category: None
Severity: 4 - Important
Item Group: None
Status: None
Privacy: Public
Assigned to: None
Open/Closed: Open
Discussion Lock: Any
_______________________________________________________
Details:
Hello,
In Guile 1.8 and earlier, `scm_c_define_gsubr ()', `gh_new_procedure ()' and
related functions take a function pointer as an argument, where the function
type uses empty parentheses (which means that the function can have any
prototype, provided the return type matches).
Function declarators with empty parentheses are not available in C++ [0] and
are an obsolescent feature as of C99 (Section 6.11.6); it also break when
GCC's `-Wstrict-prototypes' option is used [1].
Therefore, Guile's API should eventually (e.g., in the next major release) be
changed to use a different function pointer type. Hopefully, the change can
be made almost transparent for applications that use `guile-snarf'.
Thanks,
Ludovic.
[0] http://article.gmane.org/gmane.lisp.guile.user/6613
[1] http://thread.gmane.org/gmane.comp.encryption.gpg.gnutls.devel/2118
_______________________________________________________
Reply to this item at:
<http://savannah.gnu.org/bugs/?23681>
_______________________________________________
Message sent via/by Savannah
http://savannah.gnu.org/
next reply other threads:[~2008-06-23 11:45 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-23 11:45 Ludovic Courtès [this message]
2010-08-18 13:51 ` [bug #23681] Function declarators with empty parentheses should not be used Ludovic Courtès
2011-02-13 11:31 ` Ludovic Courtès
2011-02-13 13:54 ` Ludovic Courtès
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=20080623-114546.sv15145.2251@savannah.gnu.org \
--to=invalid.noreply@gnu.org \
--cc=bug-guile@gnu.org \
--cc=ludo@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).