[Cocci] Automatic program repair workshop in London
All, Papers We Love is running a workshop in London on automatic program repair, and Coccinelle's very own Julia Lawall is speaking: "Coccinelle: 10 Years of Automated Evolution in the Linux Kernel" The date is 19 January (a Sunday afternoon). Sign up (it's free) here: https://www.meetup.com/Papers-We-Love-London/events/266943387/ -- 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
[Cocci] Coccinelle has some competition
All, Coccinelle has some competition: https://comby.dev/ The market must be hotting up. Will we be seeing Julia making IPO plans ;-) -- 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] award for Coccinelle paper
Julia, ACM Software award? Nobel prize? (perhaps not...) Nobel prize for??? Literature? The Turing award seems to generate the most publicity. http://shape-of-code.coding-guidelines.com/2018/04/19/influential-philosophers-of-source-code/ -- 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] award for Coccinelle paper
Julia, received the Eurosys "Test of Time" award. Many thanks to everyone on this list who has helped to make this possible. Warming people up, ready for the major award for Coccinelle -- 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
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
Julia,
I don't think that is what it is. The declarations are eg:
static inline __printf(2, 3)
void _dev_info(const struct device *dev, const char *fmt, ...)
{}
I guess that the whole first line is part of the declaration of _dev_info,
but Coccinelle can't cope with the __printf(2, 3).
https://stackoverflow.com/questions/17825588/what-does-this-generic-function-do
Skip to ; is a remarkably effective syntax error recovery strategy.
The parser needs to restart at a top-level declaration. It's a yacc-based
parser. We can't recover within the parsing process. Perhaps it would be
possible to remove what was betwen two ;s around the line and column with
the error, but it seems like there could be a risk of making things worse.
If it's yacc based you can recover where ever you like. Knowing how to
do it is something of a black art.
Bison supports a technique that does not require wearing a pointy hat:
stmt_list: error ';' |
stmt_list error ';' ;
where error represents the something-went-wrong token.
--
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] Red Hat Women in open source award
Julia, If you care to put in a vote for me/Coccinelle... I would be happy to vote for you, but do you really want to win this? The women on the academic side are all students and yours is the only name I recognise on the community list. https://www.redhat.com/en/about/women-in-open-source julia ___ Cocci mailing list Cocci@systeme.lip6.fr https://systeme.lip6.fr/mailman/listinfo/cocci -- 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] version 1.0.0
Sébastien, However, improving the user documentation is part of what I am supposdd to do on Coccinelle dugring this year. That's why, I'd be interested in any feedback. In particular, if you could let me know which are the areas which, according to you, are not so well documented, that woudl be helpful. More and more people are hosting their documentation on github, written using markdown. https://help.github.com/articles/github-flavored-markdown/ Some examples: https://github.com/showcases/writing This approach also makes it easier for you to allow others to contribute. -- 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] version 1.0.0
Julia, Coccinelle version 1.0.0 is released. Congratulations! It must be over 10 years since I first started using Coccinelle. Should I pencil in 2025 for the release of version 2 ;-) -- 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] In depth docs question about include
Julia, Ok. Pity. What’s the preferred way for newcomers to ask questions, then? This email list? IRC? Email is preferred, because then others can benefit from your question. Don't you star in some tutorial videos from a coccinelle workshop? -- 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] s390/net: Deletion of unnecessary checks before two function calls
Dan The truth is I think that all these patches are bad and they make the code harder to read. I disagree, I think the code requires less effort to read without the if test. A developer reading the code will wonder why kfree does not handle the case when its argument is NULL. This takes effort. Now there might be a reason while kfree (or any other function) does not handle NULL, in which case the test is necessary for that reason. Or perhaps calling kfree has other consequences and this means it is good to minimise the number of calls, fair enough. The if statements are there for *human* readers to understand and you are making it harder for humans to understand the code. The reverse is true. But if there are other reasons, then leave the test in. -- Derek M. Jones tel: +44 (0) 1252 520 667 Knowledge Software Ltd blog:shape-of-code.coding-guidelines.com Software analysis http://www.knosof.co.uk ___ Cocci mailing list Cocci@systeme.lip6.fr https://systeme.lip6.fr/mailman/listinfo/cocci
Re: [Cocci] Improvements for source code analysis with inclusion of header files
Julia, Not sure what more documentation one would want. Coccinelle is getting to be widely used. When is the O'Reilly book coming out :-) -- Derek M. Jones tel: +44 (0) 1252 520 667 Knowledge Software Ltd blog:shape-of-code.coding-guidelines.com Software analysis http://www.knosof.co.uk ___ Cocci mailing list Cocci@systeme.lip6.fr https://systeme.lip6.fr/mailman/listinfo/cocci
