From: Markus Elfring <Markus.Elfring@web.de>
To: Julia Lawall <julia.lawall@lip6.fr>
Cc: Coccinelle <cocci@systeme.lip6.fr>
Subject: Re: [Cocci] Checking uniqueness for source code positions during SmPL data processing
Date: Mon, 22 Apr 2019 11:26:53 +0200 [thread overview]
Message-ID: <b09012f1-679e-6503-b040-488979614f24@web.de> (raw)
In-Reply-To: <alpine.DEB.2.21.1904221105120.3142@hadrien>
>> Where does the added number come from for the identifier “reg1”?
>
> It's in the source code, at a different position than the reg result.
You (and the script variant “list_duplicate_statement_pairs_from_if_branches6.cocci”)
are right. A bit of exception handling code can be repeated too often
in two function implementations from the source file “stv0297.c”
according to the Linux coding style, can't it?
Will software development challenges be reconsidered around the shown
source code analysis approach together with the SmPL setting “forall”?
Regards,
Markus
_______________________________________________
Cocci mailing list
Cocci@systeme.lip6.fr
https://systeme.lip6.fr/mailman/listinfo/cocci
prev parent reply other threads:[~2019-04-22 9:27 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-22 7:49 [Cocci] Checking uniqueness for source code positions during SmPL data processing Markus Elfring
2019-04-22 7:55 ` Julia Lawall
2019-04-22 8:55 ` Markus Elfring
2019-04-22 9:05 ` Julia Lawall
2019-04-22 9:26 ` Markus Elfring [this message]
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=b09012f1-679e-6503-b040-488979614f24@web.de \
--to=markus.elfring@web.de \
--cc=cocci@systeme.lip6.fr \
--cc=julia.lawall@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).