Skip to content

HTTPS clone URL

Subversion checkout URL

You can clone with
or
.
Download ZIP
Release tracking for the Coccinelle project
OCaml C Makefile Python Shell Emacs Lisp Other
Branch: master

Release of Coccinelle v1.02.

latest commit a46bef7016
Coccinelle authored rrhansen committed
Failed to load latest commit information.
bundles Coccinelle release 1.0.1
commons Release of Coccinelle v1.02.
ctl Release of Coccinelle v1.02.
demos Release of Coccinelle v1.02.
docs Release of Coccinelle v1.02.
editors Release of Coccinelle v1.02.
engine Release of Coccinelle v1.02.
extra Release of Coccinelle v1.02.
globals Release of Coccinelle v1.02.
ocaml Release of Coccinelle v1.02.
parsing_c Release of Coccinelle v1.02.
parsing_cocci Release of Coccinelle v1.02.
popl Release of Coccinelle v1.02.
popl09 Release of Coccinelle v1.02.
python Release of Coccinelle v1.02.
scripts Release of Coccinelle v1.02.
setup Release of Coccinelle v1.02.
tests Release of Coccinelle v1.02.
tools Release of Coccinelle v1.02.
Makefile Release of Coccinelle v1.02.
Makefile.am - Try to do better pretty printing when array elements are individually
Makefile.common Release of coccinelle-1.0.0-rc23
Makefile.config.in Release of Coccinelle v1.02.
Makefile.dev Release of Coccinelle v1.02.
Makefile.libs Release of coccinelle-1.0.0-rc24
Makefile.release Release of Coccinelle v1.02.
_tags - Try to do better pretty printing when array elements are individually
authors.txt Release of Coccinelle v1.02.
autogen Release of Coccinelle v1.02.
bugs.txt Coccinelle release 1.0.0-rc19
changes.txt Release of Coccinelle v1.02.
cocci.ml Release of Coccinelle v1.02.
cocci.mli Coccinelle release 1.0.1
configure Release of Coccinelle v1.02.
configure.ac Release of Coccinelle v1.02.
copyright.txt Release coccinelle-0.2.1-rc1
credits.txt Release of Coccinelle v1.02.
empty.h Release coccinelle-0.1
empty.iso Release coccinelle-0.1
env.csh Release coccinelle-0.2.0rc1
env.sh Release of Coccinelle v1.02.
flag_cocci.ml Coccinelle version 1.0.0 is released.
install.txt Release of Coccinelle v1.02.
license.txt Release coccinelle-0.1
main.ml Release of Coccinelle v1.02.
myocamlbuild.ml.in - Try to do better pretty printing when array elements are individually
readme.txt Release of Coccinelle v1.02.
release.nix Release of Coccinelle v1.02.
standard.h Release of Coccinelle v1.02.
standard.iso Release of Coccinelle v1.02.
testing.ml Release of Coccinelle v1.02.
testing.mli Coccinelle release 1.0.1
version Release of Coccinelle v1.02.
version.ml.in Coccinelle release 1.0.0-rc13
version.sh Release of Coccinelle v1.02.

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.)
Something went wrong with that request. Please try again.