From: Markus Elfring <Markus.Elfring@web.de>
To: Wolfram Sang <wsa+renesas@sang-engineering.com>, cocci@inria.fr
Subject: Re: [cocci] Deleting unwanted semicolons (with SmPL)?
Date: Mon, 8 Jul 2024 12:23:27 +0200 [thread overview]
Message-ID: <52a3a068-ab11-4de0-b63e-55319cdb9be6@web.de> (raw)
In-Reply-To: <Zou37OqG4xxBxKdm@shikoro>
>>> How should coccinelle transfer this incomplete function body to an AST?
>>
>> I hope that the support will grow also for advanced handling of abstract
>> syntax trees and semantic graphs.
>
> What approach would you suggest to create an AST from an incomplete function?
The semantic patch language was developed to handle the discussed source code
search and transformation pattern (in principle), wasn't it?
Unfortunately, there are some known software limitations involved so far.
https://gitlab.inria.fr/coccinelle/coccinelle/-/blob/d657cc2613877729ae3fbf33c5e935f927b23cdc/docs/manual/cocci_syntax.tex#L1771
https://github.com/coccinelle/coccinelle/blob/ac9af0e8b7c76341de1999389ce285b72ebaf81b/docs/manual/cocci_syntax.tex#L1771
Various open issues point further development opportunities out,
don't they?
I became curious under which circumstances corresponding software improvements
can be achieved.
Regards,
Markus
prev parent reply other threads:[~2024-07-08 10:23 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-07 12:14 [cocci] Deleting unwanted semicolons (with SmPL)? Markus Elfring
2024-07-07 13:32 ` Wolfram Sang
2024-07-07 14:32 ` Markus Elfring
2024-07-07 14:37 ` Julia Lawall
2024-07-07 14:46 ` Markus Elfring
2024-07-08 9:57 ` Wolfram Sang
2024-07-08 10:23 ` 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=52a3a068-ab11-4de0-b63e-55319cdb9be6@web.de \
--to=markus.elfring@web.de \
--cc=cocci@inria.fr \
--cc=wsa+renesas@sang-engineering.com \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).