From: Julien Signoles <julien.signoles@gmail.com>
To: Caml List <caml-list@inria.fr>
Subject: [Caml-list] Frama-C Nitrogen-20111001
Date: Mon, 10 Oct 2011 16:39:06 +0200 [thread overview]
Message-ID: <CAPczgCB0_9XngmTHs1-dyCD7KQwO_ufTC--vJ1f4w4XOb2FN_A@mail.gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1537 bytes --]
Dear all,
We are glad to announce a new major release of the static analysis tool
Frama-C, namely Nitrogen-20111001. Frama-C is fully written in OCaml. You
can write your own plug-in in OCaml too.
========
DOWNLOAD
========
You can download the release at http://frama-c.com/download.html .
For now, there is a source tar-ball distribution without the Jessie plug-in,
but including the WP plug-in. Binary versions will be released as soon as
possible. A new version of Why which includes the Jessie plug-in will
shortly be released separately by Inria and will be compatible with Frama-C
Nitrogen.
============
MAIN CHANGES
============
This new major version includes too many bug fixes and improvements to list
here: the detailed list is available at http://frama-c.com/Changelog.html .
Major improvements benefit:
- Value Analysis plug-in
- PDG plug-in and its derivatives (Slicing, Impact, Scope, Sparecode)
- Aoraï plug-in
- the GUI
- kernel property statuses
For plug-in developers: this major release changes several Frama-C APIs in
an incompatible way. A subset of the plug-in side changes can automatically
be applied by using the script bin/carbon2nitrogen.sh of the source
distribution. Complex plug-ins should be reviewed for compatibility.
======
ENJOY!
======
Enjoy this release and do not hesitate to report any issue and/or successes
with this version through the usual channels, listed at
http://frama-c.com/support.html .
Have fun with Frama-C,
Julien Signoles
[-- Attachment #2: Type: text/html, Size: 1920 bytes --]
reply other threads:[~2011-10-10 14:39 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAPczgCB0_9XngmTHs1-dyCD7KQwO_ufTC--vJ1f4w4XOb2FN_A@mail.gmail.com \
--to=julien.signoles@gmail.com \
--cc=caml-list@inria.fr \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox