cocci.inria.fr archive mirror
 help / color / mirror / Atom feed
From: Markus Elfring <Markus.Elfring@web.de>
To: Julia Lawall <julia.lawall@lip6.fr>
Cc: Coccinelle <cocci@systeme.lip6.fr>
Subject: Re: [Cocci] Concerns around type safety for usage of expressions
Date: Fri, 22 Nov 2019 11:00:30 +0100	[thread overview]
Message-ID: <46f7430f-8176-27ed-1150-af9fc69b03a7@web.de> (raw)
In-Reply-To: <alpine.DEB.2.21.1911221050320.2793@hadrien>

>>> You can specify the type of an expression rather than just expression.
>>
>> How is this approach different from the search for “specific data types”
>> (which I know already)?
>
> I have no idea what you are referring to.

Do you find it easier to clarify transformation possibilities around
applications of a macro like “COPY_ARRAY”?
https://github.com/git/git/blob/d966095db01190a2196e31195ea6fa0c722aa732/git-compat-util.h#L889

Regards,
Markus
_______________________________________________
Cocci mailing list
Cocci@systeme.lip6.fr
https://systeme.lip6.fr/mailman/listinfo/cocci

  reply	other threads:[~2019-11-22 10:00 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-11-22  9:24 [Cocci] Concerns around type safety for usage of expressions Markus Elfring
2019-11-22  9:27 ` Julia Lawall
2019-11-22  9:45   ` Markus Elfring
2019-11-22  9:50     ` Julia Lawall
2019-11-22 10:00       ` Markus Elfring [this message]
2019-11-22 10:34         ` Julia Lawall
2019-11-22 10:44           ` Markus Elfring
     [not found]             ` <alpine.DEB.2.21.1911221155320.2793@hadrien>
2019-11-22 11:20               ` Markus Elfring
2019-11-22 12:53                 ` Julia Lawall
2019-11-22 13:17                   ` Markus Elfring
2019-11-22 14:56                   ` Markus Elfring
2019-11-22 15:10                     ` Julia Lawall
2019-11-22 15:19                       ` Markus Elfring
2019-11-23  7:55                       ` [Cocci] Checking influence of variability with SmPL Markus Elfring
2019-11-23 19:36                         ` Julia Lawall
2019-11-24 10:40                           ` 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=46f7430f-8176-27ed-1150-af9fc69b03a7@web.de \
    --to=markus.elfring@web.de \
    --cc=cocci@systeme.lip6.fr \
    --cc=julia.lawall@lip6.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 NNTP newsgroup(s).