From: elfring@users.sourceforge.net (SF Markus Elfring)
To: cocci@systeme.lip6.fr
Subject: [Cocci] Checking source code (including optional parts) with SmPL
Date: Thu, 18 May 2017 15:00:35 +0200 [thread overview]
Message-ID: <02b53afb-5d87-e15f-7862-b888bb102bca@users.sourceforge.net> (raw)
In-Reply-To: <c77fb009-04c5-c381-e016-549cd7592059@users.sourceforge.net>
I would like to clarify the possibilities for corresponding software extensions
a bit more.
The Coccinelle software provides also the search operator ?question mark? which
denotes code on a specific line as optional.
https://github.com/coccinelle/coccinelle/blob/9b5e00862900b0daadf1819a6894d31544a3ba34/docs/manual/cocci_syntax.tex#L1067
The scope of the special code there is only the marked line so that I see some
software development challenges to pack desired search filters into one line.
* How often do you check the handling for optional parts?
- Do you find it relevant to check for the assignment of an error code to an
other variable?
- Are special constraints needed for additional function calls?
* How are the chances to improve readability and maintainability for SmPL code?
Regards,
Markus
next prev parent reply other threads:[~2017-05-18 13:00 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-14 15:41 [Cocci] Checking exception handling implementations with SmPL SF Markus Elfring
2017-05-18 13:00 ` SF Markus Elfring [this message]
2017-05-18 15:21 ` [Cocci] Safe determination of function properties for SmPL scripts SF Markus Elfring
2017-05-18 16:00 ` [Cocci] Checking failure predicates with SmPL SF Markus Elfring
2017-05-23 9:01 ` [Cocci] Easier search for assignment targets " SF Markus Elfring
2017-05-23 9:06 ` Julia Lawall
2017-05-23 10:52 ` 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=02b53afb-5d87-e15f-7862-b888bb102bca@users.sourceforge.net \
--to=elfring@users.sourceforge.net \
--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