From: Markus Elfring <Markus.Elfring@web.de>
To: cocci@inria.fr
Subject: [cocci] Further adjustments for pretty-printing (with SmPL)?
Date: Fri, 29 Mar 2024 10:45:58 +0100 [thread overview]
Message-ID: <88ed7db9-4163-4916-a0d1-efcc35030fca@web.de> (raw)
Hello,
I tend to prefer script variants for the semantic patch language
which specify only required changes.
Thus I would like to avoid SmPL code which expresses the deletion of additional
source code so that it can be readded almost at the same place.
This desire can occasionally trigger a questionable “side effect”.
The adjusted source code became intentionally shorter.
But the affected code might still be distributed over multiple lines
like it can often happen with argument lists for function (or macro) calls.
I noticed then that pretty-printing concerns can become more relevant.
* Reduction of indentation
* Reconsideration for the layout of involved parameter (or expression) lists
How will corresponding improvement possibilities evolve?
Regards,
Markus
reply other threads:[~2024-03-29 9:46 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=88ed7db9-4163-4916-a0d1-efcc35030fca@web.de \
--to=markus.elfring@web.de \
--cc=cocci@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 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).