All of lore.kernel.org
 help / color / mirror / Atom feed
From: Julia Lawall <julia.lawall@inria.fr>
To: Markus Elfring <Markus.Elfring@web.de>
Cc: Jakob Koschel <jkl820.git@gmail.com>,
	Julia Lawall <julia.lawall@inria.fr>,
	 cocci@inria.fr
Subject: Re: [cocci] Working with parameter/expression lists by SmPL
Date: Sun, 21 Aug 2022 11:09:38 +0200 (CEST)	[thread overview]
Message-ID: <alpine.DEB.2.22.394.2208211108400.3263@hadrien> (raw)
In-Reply-To: <26cfb01d-0d74-1c34-ac60-664c61931f07@web.de>

[-- Attachment #1: Type: text/plain, Size: 1255 bytes --]

Jakob,

Despite the bizarre way in which Markus asks the question, the ; at the
end of the comment could be a serious problem.  Could you repost your
semantic patch and test code?

thanks,
julia






On Sun, 21 Aug 2022, Markus Elfring wrote:

> > I'm not sure what you mean "link for this evolving information source". There is no
> > public information on this yet since it's an ongoing project.
>
>
> Are you looking for contributions from related research groups?
>
>
>
> >> Are you looking for better source code formatting according to semicolons?
> > I'm not exactly sure what you mean with that?
>
>
> Do you care if a bit of code which is probably relevant for the programming
> language syntax would be commented out as it was indicated by the diff fragment
> “+    // test;”?
>
>
> > I've only used adding the comment to see if the matching works correctly,
>
>
> Would other code variants (than C++-style comments) be more helpful for
> the demonstration of desirable transformation effects?
>
>
> > I'm not intending to do anything with comments in the final version.
>
>
> My software application expectations evolved into additional directions
> according to mentioned change specifications (in SmPL code).
>
> Regards,
> Markus
>
>

  reply	other threads:[~2022-08-21  9:09 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-08-16  8:54 [cocci] match arbitrary argument position Jakob Koschel
2022-08-16 11:37 ` Julia Lawall
2022-08-16 12:35   ` Jakob Koschel
2022-08-16 17:55     ` Markus Elfring
2022-08-17 14:26       ` Jakob Koschel
2022-08-17 19:21         ` Markus Elfring
2022-08-16 21:07     ` Julia Lawall
2022-08-17 14:18       ` Jakob Koschel
2022-08-17 14:36         ` Julia Lawall
2022-08-17 14:50           ` Jakob Koschel
2022-08-17 15:26             ` Julia Lawall
2022-08-17 19:48           ` [cocci] Working with parameter/expression lists by SmPL Markus Elfring
2022-08-18 12:51             ` Jakob Koschel
2022-08-18 17:42               ` Markus Elfring
2022-08-19  9:12                 ` Jakob Koschel
2022-08-19  9:57                   ` Julia Lawall
2022-08-19 10:00                     ` Jakob Koschel
2022-08-19 17:00                   ` Markus Elfring
2022-08-20 12:57                     ` Jakob Koschel
2022-08-21  8:10                       ` Markus Elfring
2022-08-21  9:09                         ` Julia Lawall [this message]
2022-08-21  9:46                           ` Markus Elfring
2022-08-21 10:01                             ` Julia Lawall
2022-08-21 11:33                               ` Markus Elfring
2022-08-18 18:00               ` [cocci] Checking a comment addition 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=alpine.DEB.2.22.394.2208211108400.3263@hadrien \
    --to=julia.lawall@inria.fr \
    --cc=Markus.Elfring@web.de \
    --cc=cocci@inria.fr \
    --cc=jkl820.git@gmail.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 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.