From: elfring@users.sourceforge.net (SF Markus Elfring)
To: cocci@systeme.lip6.fr
Subject: [Cocci] Determination of syntax scopes with SmPL
Date: Thu, 3 Dec 2015 10:20:13 +0100 [thread overview]
Message-ID: <5660094D.2040206@users.sourceforge.net> (raw)
Hello,
The Coccinelle software takes special care for some details from source files.
These details correspond to specific data structures which are connected with
a syntax for their elements. Each structure member needs usually to be processed
in the context of the involved data type hierarchy.
I find that there are further software development challenges to express
special dependendencies and constraints for advanced source code analysis with
the semantic patch language around safe handling of syntax scopes like
the following.
1. Preprocessor statements
2. Function implementation
3. Global scope
I am looking for a bit more advice around data processing of identifiers
which can appear in ordinary C functions and the statement "#define".
How should an identifier be distinguished from its use within macro text
and at other source code places?
The SmPL ellipsis can be restricted to some degree.
http://coccinelle.lip6.fr/docs/main_grammar008.html#NEST
Does this construct need any extensions to limit a source code search on
a specific scope in the mentioned hierarchy?
Regards,
Markus
reply other threads:[~2015-12-03 9:20 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=5660094D.2040206@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.