All of lore.kernel.org
 help / color / mirror / Atom feed
From: elfring@users.sourceforge.net (SF Markus Elfring)
To: cocci@systeme.lip6.fr
Subject: [Cocci] Source code analysis for header files
Date: Sun, 25 Jan 2015 18:55:32 +0100	[thread overview]
Message-ID: <54C52E14.50707@users.sourceforge.net> (raw)
In-Reply-To: <54AD5AF8.3020508@users.sourceforge.net>

> I suggest to select an alternative file extension filter for the source file
> search which is provided by your software.

I have used another simple file extension filter in my evolving source code
analysis approach. Some data were imported from header files of the software
"Linux next-20150123" into a database.

I guess that I can reuse them only in consistent ways if corresponding
name space issues will be resolved.
How should be determined with the Coccinelle technology if the collected
information is really included by a specific source file?

Regards,
Markus

      reply	other threads:[~2015-01-25 17:55 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
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 [this message]

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=54C52E14.50707@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.