caml-list - the Caml user's mailing list
 help / color / mirror / Atom feed
From: "forum@x9c.fr" <forum@x9c.fr>
To: caml users <caml-list@inria.fr>
Cc: x9c <forum@x9c.fr>
Subject: [ANN] Bisect / Bolt / Kaputt: 1.0-beta releases
Date: Sun, 31 May 2009 17:37:08 +0200	[thread overview]
Message-ID: <69904DE5-23FD-476E-B9A4-8D1A80ED42CD@x9c.fr> (raw)

This post announces the 1.0-beta release of the following projects:
   - Bisect: coverage tool
   - Bolt: logging tool
   - Kaputt: testing tool


=== Bisect ===
Home page: http://bisect.x9c.fr
Main changes since 1.0-alpha:
   - switch to OCaml 3.11.0
   - bug #30: incorrect detection of ocamljava
   - bug #31: default make target
   - bug #32: incorrect source rendering under Firefox
   - bug #33: information about global coverage missing
   - bug #34: bare text mode added
   - bug #35: introduction of navigation bar and code folding
   - bug #36: instrumentation with -unsafe switch
   - bug #37: incorrect handling of array literals
   - unreported bug regarding the handling of if/then construct with  
no else
   - introduction of CSV, XML modes
   - major code refactoring and improvement


=== Bolt ===
Home page: http://bolt.x9c.fr
First public release, main features:
   - inspired by and modeled after the Apache log4j framework
   - camlp4 syntax extension to remove logging statements at
     compile time
   - configuration of logging at runtime through property file
   - predefined output formats: text, CSV, HTML, XML
   - fully customizable


=== Kaputt ===
Home page: http://kaputt.x9c.fr
Main changes since 1.0-alpha:
   - 'Assert.assert_xyz' functions renamed to 'Assert.xyz'
     (old functions are temporary kept as 'deprecated')
   - support for Big_int, Num, Map, Set, Hashtbl, Queue, Stack,
     Weak, and Bigarray
   - support for shell-based tests
   - new output modes (HTML, XML, and CSV)


Xavier Clerc


                 reply	other threads:[~2009-05-31 15:37 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=69904DE5-23FD-476E-B9A4-8D1A80ED42CD@x9c.fr \
    --to=forum@x9c.fr \
    --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;
as well as URLs for NNTP newsgroup(s).