[Cocci] Coccinelle v1.0.5

[Cocci] Coccinelle v1.0.5

[Julia Lawall]

Coccinelle v1.0.5 is now available.  Here are the main changes:

* Python 3 is now supported.  Regrettably, this required changes to Pycaml
such that only the version distributed as part of Coccinelle can be used.
We hope to improve this situation in the future, but this strategy seemed
to be the most expeditious one to be able to make a release.

* A --tmp-dir option is available to name the directory that should hold
the output generated when using the -j.  Preiously, the name of this
directory was determined automatically from the semantic patch.

* --defined and --undefined arguments now apply to #if as well as #ifdef.

* Coccinelle is compatible with the latest release of OCaml, version
4.03.0

* Include files are now parse before the .c files that include them (quite
strangely, they were previously parsed afterwards).  This makes more
typedef information available when parsing the .c file, and can reduce
parse errors.

* Various improvements in the pretty printing of C code.

* Python support for some features that were previously only available in
OCaml scripts, namely iteration (see demos/python_iteration.{c,cocci}) and
construction of metavariable values of various types
(tests/python_mdecl.{c,cocci} and tests/python_mdeclp.{c,cocci})

A more complete list of changes, including to the pycocci wrapper, is
available here: http://coccinelle.lip6.fr/distrib/changes.html

julia

[Cocci] Further software updates after Coccinelle v1.0.5?

[SF Markus Elfring]

> Coccinelle v1.0.5 is now available.

Thanks for this software development progress.


* I would appreciate that corresponding changes will become viewable
also by the GitHub interface shortly.

* Would you like to add any comments to open issues like the following?


> * Coccinelle is compatible with the latest release of OCaml, version 4.03.0

Software development challenges around OCaml-SmPL scripting interface
with OCaml (>= 4.02.1 ?)
https://github.com/coccinelle/coccinelle/issues/48


> * Include files are now parse before the .c files that include them (quite
> strangely, they were previously parsed afterwards).  This makes more
> typedef information available when parsing the .c file, and can reduce
> parse errors.

* Was another test case added for this implementation detail?
* Is such header file inclusion still affected by command line parameters?


> * Various improvements in the pretty printing of C code.

Will further considerations evolve around the topic "Make change
influence configurable for coding style rules"?
https://github.com/coccinelle/coccinelle/issues/37


> A more complete list of changes, including to the pycocci wrapper,
> is available here: http://coccinelle.lip6.fr/distrib/changes.html

How do you think about to take another look here?

* Improve application programming interface design around match
management functions
  https://github.com/coccinelle/coccinelle/issues/64

* Fixed: PCRE bundle
 
https://github.com/coccinelle/coccinelle/commit/4ab8c0f230fe5b88c4fda55fba8137fc2e7d3f5d#diff-330c4cdb11d3a4bcb8e1446ed8022389R48

Regards,
Markus

[Cocci] Further software updates after Coccinelle v1.0.5?

[Julia Lawall]

On Mon, 6 Jun 2016, SF Markus Elfring wrote:

> > Coccinelle v1.0.5 is now available.
> 
> Thanks for this software development progress.
> 
> 
> * I would appreciate that corresponding changes will become viewable
> also by the GitHub interface shortly.

I have no idea what you are asking for.  The file changes.txt is availabl 
in github all the time.

> * Would you like to add any comments to open issues like the following?
> 
> 
> > * Coccinelle is compatible with the latest release of OCaml, version 4.03.0
> 
> Software development challenges around OCaml-SmPL scripting interface
> with OCaml (>= 4.02.1 ?)
> https://github.com/coccinelle/coccinelle/issues/48
> 
> 
> > * Include files are now parse before the .c files that include them (quite
> > strangely, they were previously parsed afterwards).  This makes more
> > typedef information available when parsing the .c file, and can reduce
> > parse errors.
> 
> * Was another test case added for this implementation detail?
> * Is such header file inclusion still affected by command line parameters?

Yes.

> 
> > * Various improvements in the pretty printing of C code.
> 
> Will further considerations evolve around the topic "Make change
> influence configurable for coding style rules"?
> https://github.com/coccinelle/coccinelle/issues/37

No idea.

julia

> 
> > A more complete list of changes, including to the pycocci wrapper,
> > is available here: http://coccinelle.lip6.fr/distrib/changes.html
> 
> How do you think about to take another look here?
> 
> * Improve application programming interface design around match
> management functions
>   https://github.com/coccinelle/coccinelle/issues/64
> 
> * Fixed: PCRE bundle
>  
> https://github.com/coccinelle/coccinelle/commit/4ab8c0f230fe5b88c4fda55fba8137fc2e7d3f5d#diff-330c4cdb11d3a4bcb8e1446ed8022389R48
> 
> Regards,
> Markus
> _______________________________________________
> Cocci mailing list
> Cocci at systeme.lip6.fr
> https://systeme.lip6.fr/mailman/listinfo/cocci
> 

[Cocci] Further software updates after Coccinelle v1.0.5?

[SF Markus Elfring]

>
>> * I would appreciate that corresponding changes will become viewable
>> also by the GitHub interface shortly.
> I have no idea what you are asking for.  The file changes.txt is availabl 
> in github all the time.

1. I have noticed that the last published commit seems to refer to a
merge (052860ee15849f96a856c253720261f350851771) from four days ago,
doesn't it?

2. A previous commit (from nine days ago) tried to express the message
"go back to version 1.0.4".

3. To which commit should the software release belong then after another
update for the involved version numbers?
   Was a Git tag introduced for the current revision identifier?

Regards,
Markus

[Cocci] Further software updates after Coccinelle v1.0.5?

[Julia Lawall]

On Mon, 6 Jun 2016, SF Markus Elfring wrote:

> >
> >> * I would appreciate that corresponding changes will become viewable
> >> also by the GitHub interface shortly.
> > I have no idea what you are asking for.  The file changes.txt is availabl 
> > in github all the time.
> 
> 1. I have noticed that the last published commit seems to refer to a
> merge (052860ee15849f96a856c253720261f350851771) from four days ago,
> doesn't it?
> 
> 2. A previous commit (from nine days ago) tried to express the message
> "go back to version 1.0.4".
> 
> 3. To which commit should the software release belong then after another
> update for the involved version numbers?
>    Was a Git tag introduced for the current revision identifier?

There is a tag for the current revision.  As it says on the Coccinelle 
website, 1.0.5 was actually released on June 2.  I only had time to make 
the announcement today.

julia

[Cocci] Further software updates after Coccinelle v1.0.5?

[SF Markus Elfring]

> There is a tag for the current revision.  As it says on the Coccinelle 
> website, 1.0.5 was actually released on June 2.  I only had time to make 
> the announcement today.

How do you think about to fix the version file at least?
https://github.com/coccinelle/coccinelle/blob/257d020a4e180641ea29a3ee568e9975b08c6ec5/version

Would you like to revert the commit "go back to version 1.0.4" eventually?

Regards,
Markus

[Cocci] Further software updates after Coccinelle v1.0.5?

[Julia Lawall]

On Mon, 6 Jun 2016, SF Markus Elfring wrote:

> > There is a tag for the current revision.  As it says on the Coccinelle 
> > website, 1.0.5 was actually released on June 2.  I only had time to make 
> > the announcement today.
> 
> How do you think about to fix the version file at least?
> https://github.com/coccinelle/coccinelle/blob/257d020a4e180641ea29a3ee568e9975b08c6ec5/version
> 
> Would you like to revert the commit "go back to version 1.0.4" eventually?

As far as I can see, the current contents of version say 1.0.5.

julia

[Cocci] Further software updates after Coccinelle v1.0.5?

[SF Markus Elfring]

> As far as I can see, the current contents of version say 1.0.5.

Unfortunately, I do not get the same impression by the GitHub display at
the moment.
Does the revision log stop with the message "go becak to version 1.0.4"
(from 2016-05-29) there?
https://github.com/coccinelle/coccinelle/commits/master/version

Regards,
Markus

[Cocci] Further software updates after Coccinelle v1.0.5?

[SF Markus Elfring]

> As far as I can see, the current contents of version say 1.0.5.

Now I can see also the desired revision identifier by a corresponding
commit from 2016-06-03 (which I missed yesterday).
https://github.com/coccinelle/coccinelle/commit/8906ed7e4dda8bd6642d4bd0dfa022e7a119f406

I am curious on how the shown software development will be continued then.

Regards,
Markus