From: elfring@users.sourceforge.net (SF Markus Elfring)
To: cocci@systeme.lip6.fr
Subject: [Cocci] Determination of statement list lengths with SmPL
Date: Thu, 28 Jul 2016 20:18:07 +0200 [thread overview]
Message-ID: <3ebc06a1-4cc8-0809-009f-2c05a427db99@users.sourceforge.net> (raw)
In-Reply-To: <alpine.DEB.2.10.1607281459000.2896@hadrien>
>> Cannot resolve PyUnicodeUCS2_AsEncodedString.
Was this issue be fixed by the commit "Updated py.ml for UCS4 support"
(fdbafd49c0f2b9267229b105beb870cfc2bd0d06 from 2016-07-16)?
>> Can the number of "steps" that were stored by a metavariable of the
>> type "statement" also be determined anyhow?
>
> No idea what you mean by steps. A statement metavariable only matches a
> single statement.
* Are "C statements" mapped to entries in a statement list metavariable
by the semantic patch language?
How do you think about to drill down from a single compound statement
to several subitems?
* Will it matter if curly brackets are occasionally missing?
Regards,
Markus
next prev parent reply other threads:[~2016-07-28 18:18 UTC|newest]
Thread overview: 41+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-26 21:12 [Cocci] version 1.0.3 released Julia Lawall
2015-10-27 9:38 ` Sébastien Hinderer
2015-10-27 10:14 ` Richard W.M. Jones
2015-10-27 10:25 ` Sébastien Hinderer
2015-10-27 11:57 ` Richard W.M. Jones
2015-10-27 12:13 ` Sébastien Hinderer
2015-10-27 12:37 ` Sébastien Hinderer
2015-10-27 21:26 ` Richard W.M. Jones
2015-10-28 7:08 ` Julia Lawall
2015-10-28 7:33 ` Julia Lawall
2015-10-28 10:13 ` Sébastien Hinderer
2015-10-28 10:51 ` Richard W.M. Jones
2015-10-28 22:06 ` [Cocci] version 1.0.4 released Julia Lawall
2016-07-19 10:05 ` Richard W.M. Jones
2016-07-19 10:07 ` Julia Lawall
2016-07-19 10:13 ` Richard W.M. Jones
2016-07-28 8:32 ` [Cocci] Determination of statement list lengths with SmPL SF Markus Elfring
2016-07-28 8:36 ` Julia Lawall
2016-07-28 8:42 ` SF Markus Elfring
2016-07-28 12:34 ` SF Markus Elfring
2016-07-28 12:38 ` Julia Lawall
2016-07-28 12:51 ` SF Markus Elfring
2016-07-28 12:59 ` Julia Lawall
2016-07-28 13:21 ` SF Markus Elfring
2016-07-28 14:30 ` Julia Lawall
2016-07-28 16:21 ` SF Markus Elfring
2016-07-28 16:26 ` Julia Lawall
2016-07-28 16:52 ` SF Markus Elfring
2016-07-28 18:18 ` SF Markus Elfring [this message]
2016-07-29 11:03 ` [Cocci] Exclusion of else branches from if statements " SF Markus Elfring
2015-10-29 10:21 ` [Cocci] Release 1.0.3: Clarification around SmPL conjunctions SF Markus Elfring
2015-10-30 13:08 ` Julia Lawall
2015-10-30 14:10 ` SF Markus Elfring
2015-10-30 14:35 ` Julia Lawall
2015-10-30 14:51 ` SF Markus Elfring
2015-10-30 15:09 ` Julia Lawall
2015-10-30 15:27 ` SF Markus Elfring
2015-10-30 15:43 ` Julia Lawall
2015-10-30 15:46 ` SF Markus Elfring
2015-10-30 16:06 ` Julia Lawall
2015-10-30 16: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=3ebc06a1-4cc8-0809-009f-2c05a427db99@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