All of lore.kernel.org
 help / color / mirror / Atom feed
From: julia.lawall@lip6.fr (Julia Lawall)
To: cocci@systeme.lip6.fr
Subject: [Cocci] Comparing statement lists with SmPL
Date: Wed, 16 Aug 2017 11:20:44 +0200 (CEST)	[thread overview]
Message-ID: <alpine.DEB.2.20.1708161119130.2730@hadrien> (raw)
In-Reply-To: <f19870ac-ba92-d635-d5b5-4d0a189e1c4e@users.sourceforge.net>



On Wed, 16 Aug 2017, SF Markus Elfring wrote:

> > Unfortunately, the software version ?1.0.6-00186-g0acd38ee? does not like this
> > SmPL specification.
>
> I overlooked to add parentheses in my evolving SmPL script.
>
> @duplicated_code@
> identifier work;
> statement s1, s2;
> statement list sl;
> type T;
> @@
>  T work(...)
>  {
>  ... when any
> (
> *if ((...) < 0) {
> *   s1
> *   s2
>     ...
> *}
> &{
>     sl
>  }
> )
>  ...
> (
> *if ((...) < 0) {
> *   s1
> *   s2
>     ...
> *}
> &{
>     sl
>  }
> )
>  ...
>  }
>
>
> The following command does not show the expected source code analysis results at the moment.
>
> elfring at Sonne:~/Projekte/Coccinelle/janitor> spatch.opt show_same_statements2.cocci ../Probe/hdsp-excerpt1.c

There is no way that I can understand the problme without having the .c
file.

Note that most of your ...s have no annotation.  So they cannot contain
what comes before or after.  I would suggest to put when any on all of the
...s here that are at statement level.

julia

>
>
> Is there any more clarification needed for the use of SmPL conjunctions?
>
> Regards,
> Markus
>

  reply	other threads:[~2017-08-16  9:20 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-08-15 17:26 [Cocci] Comparing statement lists with SmPL SF Markus Elfring
2017-08-15 17:33 ` Julia Lawall
2017-08-15 19:04   ` SF Markus Elfring
2017-08-15 19:09     ` Julia Lawall
2017-08-15 19:14       ` SF Markus Elfring
2017-08-15 20:00     ` SF Markus Elfring
2017-08-15 20:09       ` Julia Lawall
2017-08-15 20:15         ` SF Markus Elfring
2017-08-16  6:48         ` SF Markus Elfring
2017-08-16  7:03           ` SF Markus Elfring
2017-08-16  9:20             ` Julia Lawall [this message]
2017-08-16 10:42               ` SF Markus Elfring
2017-08-16  9:01           ` Julia Lawall
2017-08-16  7:35         ` SF Markus Elfring
2017-08-17 17:54           ` SF Markus Elfring
2017-08-17 18:44             ` Julia Lawall
2017-08-17 19:26               ` SF Markus Elfring
2017-08-17 19:31                 ` Julia Lawall
2017-08-17 19:43                   ` SF Markus Elfring
2017-08-22  9:19                   ` SF Markus Elfring
2017-08-22  9:28                     ` Julia Lawall
2017-08-22 10:00                       ` SF Markus Elfring
     [not found]                         ` <alpine.DEB.2.20.1708221202380.3178@hadrien>
2017-08-22 10:12                           ` SF Markus Elfring
2017-08-22 10:15                             ` Julia Lawall
2017-08-22 10:20                               ` SF Markus Elfring
     [not found]                                 ` <alpine.DEB.2.20.1708221221260.3178@hadrien>
2017-08-22 10:33                                   ` SF Markus Elfring
2017-08-23 14:43                     ` SF Markus Elfring
     [not found]                       ` <alpine.DEB.2.20.1708231644340.3150@hadrien>
2017-08-23 15:39                         ` SF Markus Elfring
     [not found]                           ` <alpine.DEB.2.20.1708231742480.3150@hadrien>
2017-08-23 15:50                             ` SF Markus Elfring
2017-08-24  7:56                             ` SF Markus Elfring
2017-08-16  6:10   ` SF Markus Elfring
2017-08-16  6:26     ` Julia Lawall
2017-08-16  6:38       ` 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=alpine.DEB.2.20.1708161119130.2730@hadrien \
    --to=julia.lawall@lip6.fr \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.