From: Christopher Li <sparse@chrisli.org>
To: Pavel Roskin <proski@gnu.org>
Cc: Randy Dunlap <rdunlap@xenotime.net>, linux-sparse@vger.kernel.org
Subject: Re: [PATCH] Re: error, types differ in signedness
Date: Mon, 5 Feb 2007 16:16:22 -0800 [thread overview]
Message-ID: <20070206001622.GB14964@chrisli.org> (raw)
In-Reply-To: <1170714431.1453.10.camel@dv>
On Mon, Feb 05, 2007 at 05:27:11PM -0500, Pavel Roskin wrote:
> I think any difference between declarations other than missing argument
> names is an example of sloppy coding and should be avoided.
The original warning about pointer signedness difference is simply wrong.
There might be value to have warning about function vs function pointer.
On the other hand, some attribute can be only specified in function prototype
declares but not the function body.
> I would prefer that sparse emits a specific warning about function vs
> function pointer mismatch. Even if it doesn't matter, it makes the code
> easier to read and safer to modify.
I did not find a easy way to do it yet.
Chris
next prev parent reply other threads:[~2007-02-06 0:44 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-05 18:54 error, types differ in signedness Randy Dunlap
2007-02-05 20:06 ` [PATCH] " Christopher Li
2007-02-05 21:04 ` Randy Dunlap
2007-02-05 22:27 ` Pavel Roskin
2007-02-06 0:16 ` Christopher Li [this message]
2007-02-06 1:12 ` Pavel Roskin
2007-02-06 18:36 ` Christopher Li
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20070206001622.GB14964@chrisli.org \
--to=sparse@chrisli.org \
--cc=linux-sparse@vger.kernel.org \
--cc=proski@gnu.org \
--cc=rdunlap@xenotime.net \
/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 NNTP newsgroup(s).