From: Julia Lawall <julia.lawall@lip6.fr>
To: "Christoph Böhmwalder" <christoph.boehmwalder@linbit.com>
Cc: Coccinelle <cocci@systeme.lip6.fr>
Subject: Re: [Cocci] const in parameter lists
Date: Thu, 12 Sep 2019 14:50:04 +0200 (CEST) [thread overview]
Message-ID: <alpine.DEB.2.21.1909121447550.2876@hadrien> (raw)
In-Reply-To: <20190912123435.ztwsymd7m4s4n6hq@gintonic.linbit>
[-- Attachment #1: Type: text/plain, Size: 2427 bytes --]
On Thu, 12 Sep 2019, Christoph Böhmwalder wrote:
> On Thu, Sep 12, 2019 at 01:31:52PM +0200, Julia Lawall wrote:
> >
> > Sorry, it's not clear to me what you want to do. Do you want to verify
> > that there is a const before renaming the parameter? Could you do
> >
> > const unsigned
> > -a
> > +b
> >
> > ?
> >
> > julia
>
> I'll try and outline what I'm actually trying to do.
>
> Here's what I have:
>
> int drbd_submit_peer_request(struct drbd_device *device,
> struct drbd_peer_request *peer_req,
> const unsigned op, const unsigned op_flags,
> const int fault_type)
> {
> // ...
> }
>
> This is what I want:
>
> int drbd_submit_peer_request(struct drbd_device *device,
> struct drbd_peer_request *peer_req,
> const unsigned rw,
> const int fault_type)
> {
> // ...
> }
>
> And this is my cocci patch:
>
> @@
> identifier op, op_flags;
> struct bio *b;
> @@
> drbd_submit_peer_request(...
> - , const unsigned op, const unsigned op_flags
> + , const unsigned rw
> ,...)
> {
> ...
> }
>
> This gives an error:
>
> minus: parse error:
> File "drbd/drbd-kernel-compat/cocci/req_write__yes_present.cocci", line 35, column 22, charpos = 548
> around = 'op',
> whole content = - , const unsigned op, const unsigned op_flags
>
>
> Doing it without the consts yields this:
>
> int drbd_submit_peer_request(struct drbd_device *device,
> - struct drbd_peer_request *peer_req,
> - const unsigned op, const unsigned op_flags,
> + struct drbd_peer_request *peer_reqconst,
> + unsigned rw,
> const int fault_type)
> {
>
> Notice the stray "const" behind "peer_req".
>
> So -- to answer your question -- my priority here is to get the code
> compiling; I don't actually care about any of the consts. Best case
> scenario would be to have it remove whether or not the consts are there
> and always add the new parameter with a const.
How about the following?
@@
identifier op, op_flags;
struct bio *b;
type T;
@@
T drbd_submit_peer_request(...,
- unsigned op
+ unsigned rw
,
- unsigned op_flags,
...)
{
...
}
It doesn't add a const on rw, though. And it doesn't allow using the
const to figure out where to match. I will have to look into why the
consts aren't being parsed properly.
julia
[-- Attachment #2: Type: text/plain, Size: 136 bytes --]
_______________________________________________
Cocci mailing list
Cocci@systeme.lip6.fr
https://systeme.lip6.fr/mailman/listinfo/cocci
next prev parent reply other threads:[~2019-09-12 12:50 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-12 11:13 [Cocci] const in parameter lists Christoph Böhmwalder
2019-09-12 11:31 ` Julia Lawall
2019-09-12 12:34 ` Christoph Böhmwalder
2019-09-12 12:50 ` Julia Lawall [this message]
2019-09-12 14:33 ` Markus Elfring
2019-09-12 14:49 ` Julia Lawall
2019-09-12 14:56 ` Markus Elfring
2019-09-14 20:00 ` Julia Lawall
2019-09-15 11:38 ` 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=alpine.DEB.2.21.1909121447550.2876@hadrien \
--to=julia.lawall@lip6.fr \
--cc=christoph.boehmwalder@linbit.com \
--cc=cocci@systeme.lip6.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;
as well as URLs for NNTP newsgroup(s).