From: elfring@users.sourceforge.net (SF Markus Elfring)
To: cocci@systeme.lip6.fr
Subject: [Cocci] Source code analysis for header files
Date: Wed, 07 Jan 2015 15:30:38 +0100 [thread overview]
Message-ID: <54AD430E.2000507@users.sourceforge.net> (raw)
In-Reply-To: <54A403EB.8080709@users.sourceforge.net>
> How do you think about an approach just to change the file
> name extension from ".c" to ".h" occasionally?
> Are there any more use cases around where
> it makes also sense to search for source files
> with other suffixes?
How easy (or challenging) is it to treat more files
as source files from the C programming language?
Would you like to extend use cases for your source code
analysis and transformation software in this design direction?
Regards,
Markus
next prev parent reply other threads:[~2015-01-07 14:30 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-31 13:20 [Cocci] Source code analysis for header files SF Markus Elfring
[not found] ` <alpine.DEB.2.10.1412311439380.2559@hadrien>
[not found] ` <54A40032.4070904@users.sourceforge.net>
[not found] ` <alpine.DEB.2.10.1412311457130.2559@hadrien>
2014-12-31 14:10 ` SF Markus Elfring
2015-01-07 14:30 ` SF Markus Elfring [this message]
2015-01-07 14:50 ` Julia Lawall
2015-01-07 15:24 ` SF Markus Elfring
2015-01-07 15:31 ` Julia Lawall
2015-01-07 15:41 ` Michael Stefaniuc
2015-01-07 15:47 ` SF Markus Elfring
2015-01-07 16:01 ` Julia Lawall
2015-01-07 16:12 ` SF Markus Elfring
2015-01-25 17:55 ` SF 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=54AD430E.2000507@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox