From: Kevin Ryde <user42@zip.com.au>
Cc: guile-devel@gnu.org
Subject: Re: [PATCH]-Wstrict-prototypes on SCM_FUNC_CAST_ARBITRARY_ARGS
Date: Sun, 21 Dec 2003 10:17:08 +1000 [thread overview]
Message-ID: <87fzffowhn.fsf@zip.com.au> (raw)
In-Reply-To: <xfy8yl7jbfh.fsf@csserver.evansville.edu> (Stephen Compall's message of "20 Dec 2003 17:50:58 -0600")
Stephen Compall <s11@member.fsf.org> writes:
>
> GCC, by default, does not produce warnings in system
> headers (i.e. libguile.h & depends).
Ah, tricky.
> If those functions have such
> parameter types, though, missing `void' where it should be, then you
> would get warnings there while compiling Guile, I should think.
Yes, except that warning isn't enabled. :)
I'd suggest putting a comment in your change about why the cast is to
"(*)(void)" where the parameter is "(*)()", in case anyone wonders
like me why they're not the same.
_______________________________________________
Guile-devel mailing list
Guile-devel@gnu.org
http://mail.gnu.org/mailman/listinfo/guile-devel
next prev parent reply other threads:[~2003-12-21 0:17 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-12-02 15:22 [PATCH]-Wstrict-prototypes on SCM_FUNC_CAST_ARBITRARY_ARGS Stephen Compall
2003-12-19 19:18 ` Kevin Ryde
2003-12-20 23:50 ` Stephen Compall
2003-12-21 0:17 ` Kevin Ryde [this message]
2004-02-14 0:17 ` Kevin Ryde
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=87fzffowhn.fsf@zip.com.au \
--to=user42@zip.com.au \
--cc=guile-devel@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).