On Tue, 22 Aug 2017, Derek M Jones wrote:
> Julia, > > > 1. More aggressive inclusion of header files, combined with caching of > > header files. Now if there is only one occurrence of a header file with a > > Caching can be dangerous because macros may be defined differently > for different includes of the same header. An option to switch off > caching could come in handy. I can add such an option. Actually, I noticed that unfolding macros can sometimes hurt more than it helps. When Coccinelle decides to unfold macros it unfolds them for all the rest of the code, but it only unfolds one level of macro. Sometimes the one-level unfolding is weirder than the original and the parser error that triggered unfoding is not related to macros anyway. So then the whole rest of the code has a weird semi-unfolded macro in it for no purpose, whe it could have compiled normally. At least for the Linux kernel, though, this seems like a rare occurrence. julia _______________________________________________ Cocci mailing list Cocci@systeme.lip6.fr https://systeme.lip6.fr/mailman/listinfo/cocci
