cocci.inria.fr archive mirror
 help / color / mirror / Atom feed
From: Julia Lawall <julia.lawall@inria.fr>
To: Markus Elfring <Markus.Elfring@web.de>
Cc: Coccinelle <cocci@systeme.lip6.fr>
Subject: Re: [Cocci] More support for SmPL data processing with databases?
Date: Mon, 13 Apr 2020 15:57:01 +0200 (CEST)	[thread overview]
Message-ID: <alpine.DEB.2.21.2004131553460.3035@hadrien> (raw)
In-Reply-To: <7228efff-76bb-44c9-e2cd-ea19bbd49abf@web.de>

I tried the following semantic patches:

@find@
expression action, check, result;
position p;
statement is, es;
@@
 result = action(...);
 if (
(   <+... result ...+>
&   check@p
)   )
    is
 else
    es

@script:ocaml@
action << find.action;
check << find.check;
p << find.p;
@@
Printf.printf "%s %s %s\n" action check (Dumper.dump p)

----------------------------

@find@
expression action, check, result;
position p;
statement is, es;
@@
 result = action(...);
 if@p (
(     <+... result ...+>
&     check
)     )
     is
 else
     es

@script:ocaml@
action << find.action;
check << find.check;
p << find.p;
@@
Printf.printf "%s %s %s\n" action check (Dumper.dump p)

On the code you provided whichis unfortunately much too long to include in
a message and that you could have surely shortened to illustrate whatever
is the problem.

I get the same output from both semantic patches, except that the line
numbers are different for the position variable p, because you have put it
in a different place.

I don't see any reason why making the script code call a database would
have any impact on this issue.

If you do get different results for the above semantic patches, please
make a small .c file that illustrates the problem.  The .c file should be
such that it illustrates the problem and no smaller file also illustrates
the problem.

julia
_______________________________________________
Cocci mailing list
Cocci@systeme.lip6.fr
https://systeme.lip6.fr/mailman/listinfo/cocci

  reply	other threads:[~2020-04-13 13:57 UTC|newest]

Thread overview: 36+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-04-10 15:07 [Cocci] Searching for functions with negative return values as error indication Markus Elfring
2020-04-10 15:12 ` Julia Lawall
2020-04-10 16:01   ` Markus Elfring
2020-04-11 13:43   ` [Cocci] Reporting variations of condition checks according to function calls Markus Elfring
2020-04-11 14:01     ` Julia Lawall
2020-04-11 14:06       ` Markus Elfring
2020-04-11 17:25       ` Markus Elfring
     [not found]         ` <alpine.DEB.2.21.2004112036270.2369@hadrien>
2020-04-11 18:50           ` Markus Elfring
2020-04-12  8:06           ` [Cocci] More support for SmPL data processing with databases? Markus Elfring
2020-04-12  8:51             ` Julia Lawall
2020-04-12  9:01               ` Markus Elfring
     [not found]                 ` <alpine.DEB.2.21.2004121115210.2419@hadrien>
2020-04-12  9:27                   ` [Cocci] Checking the application of the SmPL isomorphism “drop_else” Markus Elfring
2020-05-03  9:08                     ` Markus Elfring
2020-04-12 16:52               ` [Cocci] More support for SmPL data processing with databases? Markus Elfring
     [not found]                 ` <alpine.DEB.2.21.2004121904290.2419@hadrien>
2020-04-12 17:14                   ` Markus Elfring
2020-04-13  7:10                 ` Markus Elfring
     [not found]                   ` <alpine.DEB.2.21.2004130957540.3035@hadrien>
2020-04-13  8:23                     ` Markus Elfring
     [not found]                       ` <alpine.DEB.2.21.2004131029330.3035@hadrien>
2020-04-13  8:47                         ` Markus Elfring
     [not found]                           ` <alpine.DEB.2.21.2004131056350.3035@hadrien>
2020-04-13  9:03                             ` Markus Elfring
     [not found]                       ` <alpine.DEB.2.21.2004131031130.3035@hadrien>
2020-04-13  8:58                         ` Markus Elfring
2020-04-13 12:48                     ` Markus Elfring
2020-04-13 13:57                       ` Julia Lawall [this message]
2020-04-13 14:23                         ` Markus Elfring
     [not found]                           ` <alpine.DEB.2.21.2004131627470.3035@hadrien>
2020-04-13 14:50                             ` Markus Elfring
2020-04-13 14:59                               ` Julia Lawall
2020-04-13 15:19                                 ` Markus Elfring
2020-04-13 16:00                                   ` Julia Lawall
2020-04-13 16:08                                     ` Markus Elfring
2020-04-13 16:10                                       ` Julia Lawall
2020-04-13 16:14                                         ` Markus Elfring
2020-04-12 13:01           ` [Cocci] Reporting variations of condition checks according to function calls Markus Elfring
2020-04-12 13:27             ` Julia Lawall
2020-04-12 13:54               ` Markus Elfring
     [not found]                 ` <alpine.DEB.2.21.2004121624180.2419@hadrien>
2020-04-12 14:35                   ` Markus Elfring
2020-04-12 14:41                     ` Julia Lawall
2020-04-12 14:48                       ` 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.2004131553460.3035@hadrien \
    --to=julia.lawall@inria.fr \
    --cc=Markus.Elfring@web.de \
    --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).