From: Julia Lawall <julia.lawall@inria.fr>
To: Johannes Berg <johannes@sipsolutions.net>
Cc: cocci@systeme.lip6.fr
Subject: Re: [Cocci] moving variable declarations up
Date: Thu, 18 Jun 2020 07:59:45 +0200 (CEST) [thread overview]
Message-ID: <alpine.DEB.2.22.394.2006180758241.2391@hadrien> (raw)
In-Reply-To: <dfd11c78ef60afd3dd45097e9bf738499f608867.camel@sipsolutions.net>
On Wed, 17 Jun 2020, Johannes Berg wrote:
> On Wed, 2020-06-17 at 23:15 +0200, Julia Lawall wrote:
> >
> > > +T x;
> >
> > Change the + to ++
>
> Hah, I think you mentioned that to me before, but I can never remember
> what it does ...
>
> > There is no guarantee on the order in which the variables will appear.
>
> That's ok, I don't really care :)
>
> > > +
> > > E;
> > > ...
> >
> > Add when any after the ...
>
> What's the difference between "..." and "... when any"?
A ... B connects an A to the closest B, as you might like in some code
with lots of locks and unlocks. When any picks up any subsequent B, even
if there is another B between the matched A and B.
julia
_______________________________________________
Cocci mailing list
Cocci@systeme.lip6.fr
https://systeme.lip6.fr/mailman/listinfo/cocci
next prev parent reply other threads:[~2020-06-18 6:00 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-17 20:54 [Cocci] moving variable declarations up Johannes Berg
2020-06-17 21:15 ` Julia Lawall
2020-06-17 21:19 ` Johannes Berg
2020-06-17 21:47 ` Johannes Berg
2020-06-18 15:25 ` Julia Lawall
2020-06-18 15:49 ` Julia Lawall
2020-06-18 5:59 ` Julia Lawall [this message]
2020-06-18 7:37 ` Johannes Berg
[not found] <50990ed6-f5b7-c031-a5df-bdaa6863baa8@web.de>
2020-06-18 7:20 ` Johannes Berg
[not found] ` <b6ded75b-c4fe-dab6-b50a-d8ce55793b97@web.de>
2020-06-18 7:34 ` Johannes Berg
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.22.394.2006180758241.2391@hadrien \
--to=julia.lawall@inria.fr \
--cc=cocci@systeme.lip6.fr \
--cc=johannes@sipsolutions.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