From: julia.lawall@lip6.fr (Julia Lawall)
To: cocci@systeme.lip6.fr
Subject: [Cocci] Have coccinelle follow typedef ?
Date: Tue, 19 Mar 2013 18:18:26 +0100 (CET) [thread overview]
Message-ID: <alpine.DEB.2.02.1303191817500.1999@hadrien> (raw)
In-Reply-To: <1363709777.30419.20.camel@tiger2>
On Tue, 19 Mar 2013, Eric Leblond wrote:
> Hello,
>
> I've got the following construction in a code:
> typedef struct Packet_ {
> struct Flow_ * flow;
> } Packet;
> and in an other include file:
> typedef struct Flow_ {
> ...
> } Flow;
>
> My problem here is that if p is a Packet then p->flow is a Flow at least
> from a developer point of view. But coccinelle is not detecting the
> match "Flow f" do not match on a "p->flow".
>
> I've thought about adding a new isomorphism to solve this but I don't
> like the idea...
>
> How could I fix this issue ?
--all-includes?
I thik the type inferencer should be aware of typedefs, if it sees the
definition.
julia
next prev parent reply other threads:[~2013-03-19 17:18 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-19 16:16 [Cocci] Have coccinelle follow typedef ? Eric Leblond
2013-03-19 17:18 ` Julia Lawall [this message]
2013-03-19 17:53 ` Eric Leblond
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.02.1303191817500.1999@hadrien \
--to=julia.lawall@lip6.fr \
--cc=cocci@systeme.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