From: elfring@users.sourceforge.net (SF Markus Elfring)
To: cocci@systeme.lip6.fr
Subject: [Cocci] Comparing statement lists with SmPL
Date: Tue, 22 Aug 2017 12:00:35 +0200 [thread overview]
Message-ID: <d0047ca8-e724-af6b-26ac-a297ae2c34c8@users.sourceforge.net> (raw)
In-Reply-To: <alpine.DEB.2.20.1708221128420.3178@hadrien>
>> How would you like to treat variations in such log messages?
>
> They look fine as they are.
I have got other development opinions there depending on the preferred design goals.
* The mentioned small SmPL script can also help to find special differences.
* These log statements are similar (and not identical) in the code structure.
I wonder also about other marked code places how they would fit to
the search pattern.
* A test result was shown from two function implementations.
It can be nice to compare several functions.
Is it also possible that the comparison will be only performed within
the same function bodies?
Regards,
Markus
next prev parent reply other threads:[~2017-08-22 10:00 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
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 [this message]
[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=d0047ca8-e724-af6b-26ac-a297ae2c34c8@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 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.