From: elfring@users.sourceforge.net (SF Markus Elfring)
To: cocci@systeme.lip6.fr
Subject: [Cocci] Improvements for source code analysis with inclusion of header files
Date: Sun, 30 Mar 2014 15:08:36 +0200 [thread overview]
Message-ID: <53381754.3080204@users.sourceforge.net> (raw)
In-Reply-To: <alpine.DEB.2.10.1403301445260.2092@hadrien>
>> Do you distinguish headers from source files in this use case?
>
> No that I recall.
Would you like to support any variant of precompiled header files?
> The software changes, or one wants to use Coccinelle with other options,
> and then one would rather start over with a new cache.
I imagine that caches can also be generated for data representations with a
longer "life time".
> In that case, I usually limit the size of the cache as well, because the format
> is not particularly concise. This further implies that it is not useful
> to anything other than the current run.
I am becoming a bit more interested in conciseness for relevant data structures.
How can it be achieved to make the intermediate data storage useful for several
different source code analysis runs?
Regards,
Markus
next prev parent reply other threads:[~2014-03-30 13:08 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-30 11:30 [Cocci] Improvements for source code analysis with inclusion of header files SF Markus Elfring
2014-03-30 11:56 ` Julia Lawall
2014-03-30 12:13 ` SF Markus Elfring
2014-03-30 12:26 ` Julia Lawall
2014-03-30 12:33 ` SF Markus Elfring
2014-03-30 12:36 ` Julia Lawall
2014-03-30 12:44 ` SF Markus Elfring
2014-03-30 12:49 ` Julia Lawall
2014-03-30 13:08 ` SF Markus Elfring [this message]
2014-03-30 12:45 ` Derek M Jones
2014-03-30 13:00 ` 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=53381754.3080204@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.