Re: [Cocci] parsing of C code
> More importantly; does Julia like red jelly beans more than blue jelly beans? Would you like to discuss favourite sweets more than to clarify further improvements in parsing technology also for application together with the Coccinelle software? ;-) Regards, Markus ___ Cocci mailing list Cocci@systeme.lip6.fr https://systeme.lip6.fr/mailman/listinfo/cocci
Re: [Cocci] parsing of C code
On 24/08/2017 16:23, SF Markus Elfring wrote: More importantly; does Julia like red jelly beans more than blue jelly beans? * Do you find information relevant from answers to a question like “Context-free grammars versus context-sensitive grammars?”? https://stackoverflow.com/questions/8236422/context-free-grammars-versus-context-sensitive-grammars#answer-8250104 * Do the “attributes” which you would like to support trigger a need to work with context-dependent grammars? * Did you ask any other developers (or software designers) for possible solutions around the mentioned aspect? * Will the software situation improve any more also for the programming language “OCaml” (besides tools like “Menhir”)? Regards, Markus -- Derek M. Jones Software analysis tel: +44 (0)1252 520667 blog:shape-of-code.coding-guidelines.com ___ Cocci mailing list Cocci@systeme.lip6.fr https://systeme.lip6.fr/mailman/listinfo/cocci
Re: [Cocci] parsing of C code
> Parsing of foo fails due to the attribute __xxx(yyy) that Coccinelle is > not able to cope with. * Do you find information relevant from answers to a question like “Context-free grammars versus context-sensitive grammars?”? https://stackoverflow.com/questions/8236422/context-free-grammars-versus-context-sensitive-grammars#answer-8250104 * Do the “attributes” which you would like to support trigger a need to work with context-dependent grammars? * Did you ask any other developers (or software designers) for possible solutions around the mentioned aspect? * Will the software situation improve any more also for the programming language “OCaml” (besides tools like “Menhir”)? Regards, Markus ___ Cocci mailing list Cocci@systeme.lip6.fr https://systeme.lip6.fr/mailman/listinfo/cocci
Re: [Cocci] parsing of C code
>> If it's yacc based you can recover where ever you like. Knowing how to >> do it is something of a black art. > Well, ocamlyacc, to be precise. Can the software “Menhir” help any more for the needed data processing? http://gallium.inria.fr/%7Efpottier/menhir/ Regards, Markus ___ Cocci mailing list Cocci@systeme.lip6.fr https://systeme.lip6.fr/mailman/listinfo/cocci
Re: [Cocci] parsing of C code
> I have tried to improve the parsing of C code recently. This information is useful. > 1. More aggressive inclusion of header files, Why do you need to become “aggressive” there when the corresponding data processing should be just correct? > combined with caching of header files. How do you think about to configure this approach with special parameters? > flush stdout Can such a function call be omitted here? > If some functions are missing in the output when using the new version, > as compared to the output when using the old version, and if these functions > are things you might want to process in some way, thenlet me know about > the problem. I became more curious on the run time characteristics (as you already know) for the presented software evolution. I stumbled on some execution challenges during the application of special source code search patterns. How would they increase because of the desired inclusion of additional source (or header) files for analysis approaches which would need them? Regards, Markus ___ Cocci mailing list Cocci@systeme.lip6.fr https://systeme.lip6.fr/mailman/listinfo/cocci
Re: [Cocci] parsing of C code
> At least for the Linux kernel, you can't just run one make and get all the > files to be compiled. Some files are indeed very hard to compile. How do you think about to point any specific source code examples out which you find a bit too challenging so far? Regards, Markus ___ Cocci mailing list Cocci@systeme.lip6.fr https://systeme.lip6.fr/mailman/listinfo/cocci
Re: [Cocci] Comparing statement lists with SmPL
> If you like the results from the second case, what more do you want? I would like to achieve somehow that the number of presented “false positives” will become so low so that similar (and extended) SmPL scripts can be used for more automatic source code transformations with higher confidence. * How are are the chances to integrate corresponding variants into a script collection for which you care also? https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/tree/scripts/coccinelle/ * How much does the attention for related issues fit to the software development capacity which is available so far? Regards, Markus ___ Cocci mailing list Cocci@systeme.lip6.fr https://systeme.lip6.fr/mailman/listinfo/cocci
