From mboxrd@z Thu Jan  1 00:00:00 1970
From: elfring@users.sourceforge.net (SF Markus Elfring)
Date: Sun, 25 Jan 2015 18:55:32 +0100
Subject: [Cocci] Source code analysis for header files
In-Reply-To: <54AD5AF8.3020508@users.sourceforge.net>
References: <54A3F836.7060903@users.sourceforge.net>
 <alpine.DEB.2.10.1412311439380.2559@hadrien>
 <54A40032.4070904@users.sourceforge.net>
 <alpine.DEB.2.10.1412311457130.2559@hadrien>
 <54A403EB.8080709@users.sourceforge.net>
 <54AD430E.2000507@users.sourceforge.net>
 <alpine.DEB.2.10.1501071549410.3328@hadrien>
 <54AD4FC5.3000001@users.sourceforge.net>
 <alpine.DEB.2.10.1501071630480.3328@hadrien>
 <54AD552B.7040906@users.sourceforge.net>
 <alpine.DEB.2.10.1501071700190.3328@hadrien>
 <54AD5AF8.3020508@users.sourceforge.net>
Message-ID: <54C52E14.50707@users.sourceforge.net>
To: cocci@systeme.lip6.fr
List-Id: cocci@systeme.lip6.fr

> 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