From: Markus Elfring <Markus.Elfring@web.de>
To: Julia Lawall <julia.lawall@inria.fr>, cocci@inria.fr
Subject: Re: [cocci] Searching for repeated source code with SmPL?
Date: Mon, 6 May 2024 13:03:28 +0200 [thread overview]
Message-ID: <eb581667-9255-49ef-9434-2fe66e206bca@web.de> (raw)
In-Reply-To: <52305da6-998c-273c-c4cc-b8fdb1d161b@inria.fr>
>> Source code parts can occasionally be repeated.
>>
>> * Loops
>> The control flow can contain ordinary loops.
>>
>> * Recursion
>> A function may be called by itself.
>>
>>
>> Such constructs trigger special consequences also for further data processing
>> with higher level technologies.
>>
>> + Computation tree logic
>>
>> + Linear temporal logic
>>
>>
>> I am still looking for clarifications so that the Coccinelle software
>> can be applied in safer ways.
>>
>>
>> Regular expressions support some search operators for quantification.
>> A notation is accordingly supported for the specification of a minimum number
>> of matches which would be bigger than one item.
>>
>> I imagine that such functionality would be helpful also for the semantic patch language.
>> How will the chances evolve to extend corresponding quantifiers anyhow?
>> https://gitlab.inria.fr/coccinelle/coccinelle/-/blob/23f7738a7881b02d016d278ee293cfd4a126fcab/docs/manual/cocci_syntax.tex#L793
>> https://github.com/coccinelle/coccinelle/blob/755250323b80f27701e78d325cc83509197b33b1/docs/manual/cocci_syntax.tex#L793
>>
>> I would appreciate if multiple occurrences of code elements can be better detected
>> and transformed.
>
> I have no intention of adding regular expressions.
Please take another look at provided information from my clarification approach
so that undesirable misunderstandings can be better avoided.
* Regular expressions are supported already by the Coccinelle software.
+ They can be applied for advanced SmPL constraints.
+ Embedded scripts for programming languages like “OCaml” and “Python”
occasionally benefit from this technique.
> Be more concrete about what you are not able to do.
The semantic patch language supports a few “Dot variants” so far.
I am looking for further possibilities according to item quantification.
How should a search be performed for source code which would occur twice at least
(without taking repetition because of loops and recursion into account)?
How would a notation “{2,}” look like in SmPL?
https://en.wikipedia.org/wiki/Regular_expression#Basic_concepts
Regards,
Markus
next prev parent reply other threads:[~2024-05-06 11:03 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-06 10:08 [cocci] Searching for repeated source code with SmPL? Markus Elfring
2024-05-06 10:09 ` Julia Lawall
2024-05-06 11:03 ` Markus Elfring [this message]
2024-05-06 12:10 ` Markus Elfring
2024-05-06 12:16 ` Julia Lawall
2024-05-06 12:40 ` Markus Elfring
2024-05-11 15:36 ` Markus Elfring
2024-05-11 16:04 ` Julia Lawall
2024-05-11 16:35 ` Markus Elfring
2024-05-11 16:37 ` Julia Lawall
2024-05-11 17:02 ` Markus Elfring
2024-05-11 17:12 ` Julia Lawall
2024-05-11 17:21 ` Markus Elfring
2024-05-11 17:33 ` Julia Lawall
2024-05-12 6:48 ` Markus Elfring
2024-05-12 7:34 ` Julia Lawall
2024-05-12 8:01 ` Markus Elfring
2024-05-12 8:10 ` Julia Lawall
2024-05-12 8:33 ` Markus Elfring
2024-05-12 9:17 ` Julia Lawall
2024-05-12 9:30 ` Markus Elfring
2024-05-13 9:34 ` Markus Elfring
2024-05-12 11:24 ` Markus Elfring
2024-05-12 12:53 ` Julia Lawall
2024-05-12 13:07 ` Markus Elfring
2024-05-12 13:13 ` Julia Lawall
2024-05-12 13:22 ` Markus Elfring
2024-05-12 14:51 ` Markus Elfring
2024-05-12 14:57 ` Julia Lawall
2024-05-11 7:15 ` Markus Elfring
2024-05-22 8:20 ` Markus Elfring
2024-05-22 8:24 ` Julia Lawall
2024-05-22 8:44 ` Markus Elfring
2024-05-22 13:12 ` Markus Elfring
2024-05-22 15:34 ` Julia Lawall
2024-05-22 16:06 ` 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=eb581667-9255-49ef-9434-2fe66e206bca@web.de \
--to=markus.elfring@web.de \
--cc=cocci@inria.fr \
--cc=julia.lawall@inria.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.