From mboxrd@z Thu Jan  1 00:00:00 1970
From: elfring@users.sourceforge.net (SF Markus Elfring)
Date: Tue, 15 Apr 2014 08:31:01 +0200
Subject: [Cocci] Road map after Coccinelle 1.0.0-rc21?
In-Reply-To: <alpine.DEB.2.10.1404150721500.2083@hadrien>
References: <alpine.DEB.2.10.1404141356250.2601@hadrien>
 <534BDDD6.9070407@users.sourceforge.net>
 <alpine.DEB.2.10.1404141525370.2572@hadrien>
 <534BE66B.8060907@users.sourceforge.net>
 <alpine.DEB.2.10.1404141622020.2591@hadrien>
 <534BF121.40607@users.sourceforge.net>
 <alpine.DEB.2.10.1404141634180.2591@hadrien>
 <534BF3B3.90007@users.sourceforge.net>
 <alpine.DEB.2.10.1404141725420.2572@hadrien>
 <534C10AD.1080806@users.sourceforge.net>
 <alpine.DEB.2.10.1404150721500.2083@hadrien>
Message-ID: <534CD225.1010207@users.sourceforge.net>
To: cocci@systeme.lip6.fr
List-Id: cocci@systeme.lip6.fr

>> How are the chances to get the filter pattern to work which was created with an
>> alternation of 893 function names?
> 
> I have already stated that this is not a priority.

I can understand that.


> First, it is not a reasonable use of Cocinelle.

I find this feedback strange.

Static source code analysis on Linux files can result in higher and interesting
numbers for further consideration of corresponding transformations.


> Second, the problem is likely not in Coccinelle but in the regular expression library
> that is being used.

Which source code places are affected by this software development challenge?

Regards,
Markus