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 08:40:48 +0100 [thread overview]
Message-ID: <54991C80.6000508@users.sourceforge.net> (raw)
Hello,
I try to extract data and filter on properties from various
function implementations.
Now I would like to clarify consequences from the name resolution
process of the C programming language a bit more for safer
development of semantic patches.
Implementations from separate directories can provide different properties.
It can occasionally happen that functions from different folders
have got the same name.
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?
Regards,
Markus
next reply other threads:[~2014-12-23 7:40 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-23 7:40 SF Markus Elfring [this message]
2014-12-23 9:38 ` [Cocci] Dynamic construction of SmPL constraints Julia Lawall
2014-12-23 21:42 ` SF Markus Elfring
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=54991C80.6000508@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.