From: Markus Elfring <Markus.Elfring@web.de>
To: Julia Lawall <julia.lawall@inria.fr>
Cc: cocci@inria.fr, Elia Pinto <gitter.spiros@gmail.com>
Subject: Re: [cocci] Fixing the adjustment of variable declarations
Date: Sun, 13 Nov 2022 16:36:21 +0100 [thread overview]
Message-ID: <4d057f08-bae3-1762-6b4f-b8dea38ac9d9@web.de> (raw)
In-Reply-To: <d6f6d9fb-aa4b-5d17-788-e4b5f3914617@inria.fr>
>> The error message was not displayed for such a source code variant.
>>
>> I got the impression instead that multiple declarators could be handled
>> to some degree for changeable variable declarations also by the means of
>> the semantic patch language.
> That is correct. They can be handled to some degree.
Thanks for your acknowledgement.
> That doesn't contradict the message provided.
I interpret the discussed software situation differently.
Should the source code fragment “char **p, *r;” be treated as an indication for
the declaration of two variables with different (pointer) data types?
Does hinder anything to extend the support for all other data types accordingly?
Regards,
Markus
prev parent reply other threads:[~2022-11-13 15:36 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-09 11:42 [cocci] Possible bug in a semantic patch Elia Pinto
2022-11-09 11:49 ` Julia Lawall
2022-11-09 20:21 ` [cocci] Fixing the adjustment of variable declarations Markus Elfring
2022-11-11 19:10 ` [cocci] Reducing the scope for variables with SmPL Markus Elfring
2022-11-12 9:42 ` [cocci] Fixing the adjustment of variable declarations Markus Elfring
2022-11-12 10:38 ` Markus Elfring
2022-11-12 11:17 ` Julia Lawall
2022-11-12 11:45 ` Markus Elfring
2022-11-13 10:30 ` Markus Elfring
2022-11-13 10:36 ` Julia Lawall
2022-11-13 12:26 ` Markus Elfring
2022-11-13 14:10 ` Julia Lawall
2022-11-13 14:23 ` Markus Elfring
2022-11-13 14:28 ` Julia Lawall
2022-11-13 14:55 ` Markus Elfring
2022-11-13 15:19 ` Julia Lawall
2022-11-13 15:36 ` 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=4d057f08-bae3-1762-6b4f-b8dea38ac9d9@web.de \
--to=markus.elfring@web.de \
--cc=cocci@inria.fr \
--cc=gitter.spiros@gmail.com \
--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 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).