From: mstefani@redhat.com (Michael Stefaniuc)
To: cocci@systeme.lip6.fr
Subject: [Cocci] Source code analysis for header files
Date: Wed, 07 Jan 2015 16:41:41 +0100 [thread overview]
Message-ID: <54AD53B5.1030000@redhat.com> (raw)
In-Reply-To: <alpine.DEB.2.10.1501071630480.3328@hadrien>
On 01/07/2015 04:31 PM, Julia Lawall wrote:
>
>
> On Wed, 7 Jan 2015, SF Markus Elfring wrote:
>
>>>> Would you like to extend use cases for your source code
>>>> analysis and transformation software in this design
>>>> direction?
>>>
>>> There is an option --include-headers to take into account .h
>>> files. I guess there could be anoption --exclude-c-files if
>>> there is enough interest to warrant the addition of yet another
>>> option.
>>
>> An "exclude option" does not sound promising for my feature
>> request around including more possibilities, does it?
>
> I don't see the problem - C files are included by default, so one
> might perhaps want the option to exclude them.
>
> But what else is there?
`find -name \*.h` has the same length to type and is easier to remember.
That's what I use in the very few situations that I needed that feature.
bye
michael
next prev parent reply other threads:[~2015-01-07 15:41 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
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 [this message]
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=54AD53B5.1030000@redhat.com \
--to=mstefani@redhat.com \
--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