Source code of the Coccinelle project
Clone or download
JuliaLawall Add two layers of array declarations in typedef
As noted previously, this is not a general solution.
Latest commit 14ce94a Jan 12, 2019
Permalink
Type Name Latest commit message Commit time
Failed to load latest commit information.
bundles Disable maintainer mode for stdcompat Dec 24, 2018
commons Replace pidpath and realpath by pure implementations Jul 4, 2018
ctl make some not possible messages unique Sep 8, 2018
debian Get rid of the --enable-release configure option. Mar 18, 2016
demos Allow line ranges in file groups Oct 27, 2018
docs Add two layers of array declarations in typedef Jan 13, 2019
editors Remove a bunch of trailing whitespaces and blank lines at end of files. Aug 10, 2015
engine 80 char change Dec 28, 2018
extra Support for compiling single library Sep 8, 2017
globals Replace pidpath and realpath by pure implementations Jul 4, 2018
ocaml pragmas with \ after the first word Dec 13, 2018
parsing_c add nl before added struct field Jan 12, 2019
parsing_cocci Add two layers of array declarations in typedef Jan 13, 2019
popl typos Jun 9, 2017
popl09 Support for compiling single library Sep 8, 2017
python Keep whitespace before comments in statements and declarations. Aug 12, 2018
scripts Use bash instead of sh Nov 28, 2018
setup Update bundles Dec 23, 2018
tests Add two layers of array declarations in typedef Jan 13, 2019
tools add conjunction for identifiers Oct 30, 2018
.gitignore Missing configure Aug 30, 2018
.merlin Share the .merlin file. Mar 14, 2016
Makefile pcre uses stdcompat Dec 23, 2018
Makefile.am always wraps calls to pkg-config, just in case it does not have full … Aug 23, 2012
Makefile.common typos Jun 9, 2017
Makefile.config.in --with-bash-completion option Aug 6, 2018
Makefile.dev typos Jun 9, 2017
Makefile.library Support for compiling single library Sep 8, 2017
Makefile.libs Remove old reference to bundles/parmap/parmap-1.0-rc7 Jul 31, 2018
Makefile.package Fix bug preventing linking with seq, uchar and result Aug 30, 2018
Makefile.release typo Jun 9, 2017
authors.txt Remove a bunch of trailing whitespaces and blank lines at end of files. Aug 10, 2015
autogen autogen: add -Wall to the invocation of autoconf. Sep 23, 2015
bugs.txt Removed Yoann E-mail from bugs.txt Nov 29, 2013
changes.txt misc Dec 25, 2018
cocci.ml add file name to short temporary files Nov 5, 2018
cocci.mli Allow line ranges in file groups Oct 27, 2018
coccinelle.ml Keep only Regexp.* reference Feb 14, 2018
coccinelle.mli Coccinelle OCaml interface Feb 13, 2018
configure.ac Fix parmap configure path Dec 23, 2018
copyright.txt Update copyright for 2010 Jan 28, 2010
credits.txt Remove a bunch of trailing whitespaces and blank lines at end of files. Aug 10, 2015
empty.h new file Mar 27, 2008
empty.iso big refactoring Aug 6, 2006
enter.ml Update bundles Dec 23, 2018
enter.mli missing file Feb 13, 2018
env.csh Better coordination between coccinelle and coccicheck Jan 4, 2010
env.sh Remove a bunch of trailing whitespaces and blank lines at end of files. Aug 10, 2015
flag_cocci.ml move inplace flag for future use in cocci.ml Aug 21, 2017
flag_cocci.mli Missing .mlis Sep 6, 2017
install.txt Add information about parmap package on Debian-like systems Dec 11, 2018
license.txt Changed for the GPL license distributed by the FSF. Apr 13, 2016
main.ml Coccinelle OCaml interface Feb 13, 2018
main.mli Fixed Makefile Sep 6, 2017
make-release.sh Fix bin-bytecode package name Sep 12, 2018
read_options.ml close option file Jul 28, 2017
read_options.mli typos Jun 9, 2017
readme.txt Remove a bunch of trailing whitespaces and blank lines at end of files. Aug 10, 2015
standard.h drop some declares that are no longer useful May 6, 2018
standard.iso allow { ... } to turn into an arbitrary statement Dec 15, 2018
testing.ml add --expected-extension option for more testing flexibility Dec 22, 2018
testing.mli add --expected-extension option for more testing flexibility Dec 22, 2018
version Release 1.0.7 Jul 4, 2018
version.ml.in Makefile/configure tuning. Apr 13, 2012
version.sh autotools: add localversion information Aug 11, 2015

readme.txt

                            Coccinelle


Coccinelle allows programmers to easily write some complex
style-preserving source-to-source transformations on C source code,
like for instance to perform some refactorings.

To install Coccinelle from its source, see the instructions in install.txt.
Once you have installed coccinelle, there is a script 'spatch' in /usr/bin
or /usr/local/bin that invokes the Coccinelle program.

If you want to run Coccinelle without installing it, you can run the
Coccinelle program directly from the download/build directory. You may then
have to setup a few environment variables so that the Coccinelle program
knows where to find its configuration files.
For bash do:

  $ source env.sh

For tcsh do:

  $ source env.csh


You can test coccinelle with:

  $ spatch -sp_file demos/simple.cocci demos/simple.c -o /tmp/new_simple.c

If you haven't installed coccinelle, run then ./spatch or ./spatch.opt



If you downloaded the bytecode version of spatch you may first
have to install OCaml (which contains the 'ocamlrun' bytecode interpreter,
the equivalent of 'java', the Java virtual machine, but for OCaml) and then do:

  $ ocamlrun spatch -sp_file demos/simple.cocci demos/simple.c -o /tmp/new_simple.c


For more information on Coccinelle, type 'make docs' and have a look at the
files in the docs/ directory. You may need to install the texlive-fonts-extra
packages from your distribution to compile some of the LaTeX documentation
files.

 ** Runtime dependencies under Debian/Ubuntu**

 - For the OCaml scripting feature in SmPL
	ocaml-native-compilers
     or ocaml-nox

---------------------------------------------------------------------------

Contributing:

Contributions are welcome.  Please sign your contributions, according to
the following text extracted from Documentation/SubmittingPatches.txt of
the Linux kernel:

The sign-off is a simple line at the end of the explanation for the
patch, which certifies that you wrote it or otherwise have the right to
pass it on as an open-source patch.  The rules are pretty simple: if you
can certify the below:

        Developer's Certificate of Origin 1.1

        By making a contribution to this project, I certify that:

        (a) The contribution was created in whole or in part by me and I
            have the right to submit it under the open source license
            indicated in the file; or

        (b) The contribution is based upon previous work that, to the best
            of my knowledge, is covered under an appropriate open source
            license and I have the right under that license to submit that
            work with modifications, whether created in whole or in part
            by me, under the same open source license (unless I am
            permitted to submit under a different license), as indicated
            in the file; or

        (c) The contribution was provided directly to me by some other
            person who certified (a), (b) or (c) and I have not modified
            it.

	(d) I understand and agree that this project and the contribution
	    are public and that a record of the contribution (including all
	    personal information I submit with it, including my sign-off) is
	    maintained indefinitely and may be redistributed consistent with
	    this project or the open source license(s) involved.

then you just add a line saying

	Signed-off-by: Random J Developer <random@developer.example.org>

using your real name (sorry, no pseudonyms or anonymous contributions.)