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: cocci@inria.fr
Subject: Re: [cocci] Adding metavariable types for the handling of string literals?
Date: Fri, 25 Mar 2022 22:23:43 +0100 (CET)	[thread overview]
Message-ID: <alpine.DEB.2.22.394.2203252223110.4442@hadrien> (raw)
In-Reply-To: <c17bb3cc-f839-625a-66a6-2b9de96c9264@web.de>

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



On Fri, 25 Mar 2022, Markus Elfring wrote:

> Hello,
>
> The metavariable type “constant” is supported by the semantic patch language.
> Thus some data processing can be performed for literals.
>
> I would appreciate the support for metavariable types which will match only
> string literals.
> https://en.cppreference.com/w/c/language/string_literal

constant char[] x; ?

julia


>
> I guess that such a kind of metavariable would include also the enclosing
> quotation characters.
> But if captured data should be passed for further processing to another
> scripting language, it would occasionally be more helpful to omit the double
> quotes there.
> Additional programming interfaces can also help to handle data parts better,
> can't they?
>
> Would you like to work with another metavariable variant for this purpose?
>
> How will the chances evolve to extend the Coccinelle software accordingly?
>
> Regards,
> Markus
>
>

  reply	other threads:[~2022-03-25 21:23 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-03-25 21:18 [cocci] Adding metavariable types for the handling of string literals? Markus Elfring
2022-03-25 21:23 ` Julia Lawall [this message]
2022-03-25 21:33   ` Markus Elfring
2022-03-25 21:36     ` Julia Lawall
2022-03-25 21:40       ` Markus Elfring
2022-03-26  7:09   ` Markus Elfring
2022-03-27 11:31   ` Markus Elfring
2022-03-27 11:53     ` Julia Lawall
2022-03-27 12:04       ` Markus Elfring
2022-03-27 12:51         ` Julia Lawall
2022-03-27 14:12           ` Markus Elfring
2022-03-26 19:26 ` 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.2203252223110.4442@hadrien \
    --to=julia.lawall@inria.fr \
    --cc=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 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.