From: SF Markus Elfring <elfring@users.sourceforge.net>
To: Joe Perches <joe@perches.com>
Cc: Julia Lawall <julia.lawall@lip6.fr>,
Kris Borer <kborer@gmail.com>, Michal Marek <mmarek@suse.com>,
Gilles Muller <Gilles.Muller@lip6.fr>,
Nicolas Palix <nicolas.palix@imag.fr>,
linux-kernel@vger.kernel.org, cocci@systeme.lip6.fr
Subject: Re: coccinelle: add style check for assignment in if
Date: Wed, 10 Feb 2016 10:00:53 +0100 [thread overview]
Message-ID: <56BAFC45.5000003@users.sourceforge.net> (raw)
In-Reply-To: <1455062207.3333.6.camel@perches.com>
>> Can the check result display be more convenient from the semantic
>> patch script interface in comparison to the other tool?
>
> -ENOPARSE. More detail please.
Kris Borer suggested a SmPL script which can generate (only) patches
so far by the usual application of the Coccinelle software.
I assume that this approach was limited just because Julia Lawall
indicated that this functionality would be sufficient for a while.
The documentation for the command "make coccicheck" mentions
additional modes.
https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/tree/Documentation/coccinelle.txt?id=ec97946ed038f4b3faa587bc76152b198805b0c4#n170
They refer to specific output formats for the result from the
static source code analysis.
* How often would you like to look at proposed changes by the
Org mode format (of Emacs)?
http://orgmode.org/
* Do you find the report mode also useful occasionally?
Are you interested to get further output variants?
Examples:
* CSV
* XML
Regards,
Markus
next prev parent reply other threads:[~2016-02-10 9:01 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-08 12:46 [PATCH v2] coccinelle: add style check for assignment in if Kris Borer
2016-02-09 8:27 ` SF Markus Elfring
2016-02-09 9:18 ` Julia Lawall
2016-02-09 12:55 ` SF Markus Elfring
2016-02-09 23:56 ` Joe Perches
2016-02-10 9:00 ` SF Markus Elfring [this message]
2016-02-10 15:06 ` Kris Borer
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=56BAFC45.5000003@users.sourceforge.net \
--to=elfring@users.sourceforge.net \
--cc=Gilles.Muller@lip6.fr \
--cc=cocci@systeme.lip6.fr \
--cc=joe@perches.com \
--cc=julia.lawall@lip6.fr \
--cc=kborer@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mmarek@suse.com \
--cc=nicolas.palix@imag.fr \
/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