From: elfring@users.sourceforge.net (SF Markus Elfring)
To: cocci@systeme.lip6.fr
Subject: [Cocci] Dynamic construction of SmPL constraints
Date: Tue, 23 Dec 2014 22:42:25 +0100 [thread overview]
Message-ID: <5499E1C1.5070805@users.sourceforge.net> (raw)
In-Reply-To: <alpine.DEB.2.10.1412231037320.2462@hadrien>
>> I see that there are some development challenges when I would like
>> to construct SmPL constraints in the way that they will take the directory
>> hierarchy for a source file into account.
>> How can this functionality be achieved?
>
> You always have the file name information available in a position
> variable.
>
> Without knowing concretely what you want to do that is the only suggestion
> that I have.
I try to prepare my semantic patches for name space issues with the
C programming language. A few of my SmPL approaches should be applicable in
general ways so that I can avoid efforts at other places.
It seems that SmPL constraints are set up at start of the program "spatch".
I imagine that more fine-tuning will help to achieve safer and better
handling of relevant background information at the moment when a concrete
source file should be analysed.
The directory hierarchy should influence the identifier selection somehow,
shouldn't it?
Regards,
Markus
next prev parent reply other threads:[~2014-12-23 21:42 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-23 7:40 [Cocci] Dynamic construction of SmPL constraints SF Markus Elfring
2014-12-23 9:38 ` Julia Lawall
2014-12-23 21:42 ` SF Markus Elfring [this message]
2014-12-23 21:45 ` Julia Lawall
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=5499E1C1.5070805@users.sourceforge.net \
--to=elfring@users.sourceforge.net \
--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 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.