From: SF Markus Elfring <elfring@users.sourceforge.net>
To: Nicholas Mc Guire <hofrat@osadl.org>
Cc: cocci@systeme.lip6.fr, linux-kernel@vger.kernel.org
Subject: Re: [PATCH RFC] Coccinelle: Check for return not matching function signature
Date: Tue, 05 May 2015 14:32:59 +0200 [thread overview]
Message-ID: <5548B87B.4060103@users.sourceforge.net> (raw)
In-Reply-To: <1430820761-28122-1-git-send-email-hofrat@osadl.org>
> Check if the signature of a function and the return value type match.
Is this a task that is usually performed by a compiler?
> In many cases this mismatch will have no side-effects
> but in some cases it may lead to hard to locate problems
It is another software development challenge to find concrete
open issues there.
> - and for readability and code understanding it is also helpful
> when types match.
How would you like to check for compatible data types here?
> The output is a bit lengthy - not sure if that is too much
> but it seemed useful to me to see the non-matching types explicitly
> in the warning message.
How do you think about to import the result list into a database table?
> +if T1 != T2:
> + print "%s:%s,%s WARNING: return of wrong type (%s != %s)" % (p[0].file,fn,p[0].line,T1,T2)
Is such a check a bit too simple?
Regards,
Markus
next prev parent reply other threads:[~2015-05-05 12:33 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-05 10:12 [PATCH RFC] Coccinelle: Check for return not matching function signature Nicholas Mc Guire
2015-05-05 12:32 ` SF Markus Elfring [this message]
2015-05-05 13:04 ` Nicholas Mc Guire
2015-05-05 13:29 ` [Cocci] " Julia Lawall
2015-05-05 13:45 ` SF Markus Elfring
2015-05-05 14:40 ` Julia Lawall
2015-05-05 16:00 ` Nicholas Mc Guire
2015-05-05 21:24 ` Julia Lawall
2015-05-08 6:59 ` Nicholas Mc Guire
2015-05-05 16:25 ` SF Markus Elfring
2015-05-05 21:46 ` Julia Lawall
2015-05-06 7:15 ` SF Markus Elfring
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=5548B87B.4060103@users.sourceforge.net \
--to=elfring@users.sourceforge.net \
--cc=cocci@systeme.lip6.fr \
--cc=hofrat@osadl.org \
--cc=linux-kernel@vger.kernel.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