From: "Daniel Bünzli" <daniel.buenzli@erratique.ch>
To: "OCaml List" <caml-list@inria.fr>,
"mirageos-devel@lists.xenproject.org"
<mirageos-devel@lists.xenproject.org>
Cc: Jeremy Yallop <yallop@gmail.com>, Drup <drupyog@zoho.com>
Subject: [Caml-list] [ANN] Logs 0.4.2
Date: Thu, 3 Dec 2015 19:41:47 +0000 [thread overview]
Message-ID: <9FD64A9BC7C04CE0815129733504EE2E@erratique.ch> (raw)
Hello,
I'd like to announce the first release of Logs. Here's the blurb:
Logs provides a logging infrastructure for OCaml. Logging is performed
on sources whose reporting level can be set independently. Log message
report is decoupled from logging and is handled by a reporter.
A few optional log reporters are distributed with the base library and
the API easily allows to implement your own.
Logs depends only on the `result` compatibility package. The optional
`Logs_stdo` reporter on standard outputs depends on Fmt. The optional
`Logs_browser` reporter that reports to the web browser console depends
on js_of_ocaml. The optional `Logs_cli` library that provides command line
support for controlling Logs depends on `Cmdliner`.
Logs and its reporters are distributed under the BSD3 license.
Feedback on the API is welcome, it could still change a bit before stabilizing on a 1.0.0 release.
Homepage: http://erratique.ch/software/logs
API docs: http://erratique.ch/software/logs/doc
The continuation based formatting trick used by Logs for minimizing non-logging overhead is based on Jeremy Yallop's findings; Gabriel Radanne helped to make further tests. Thanks to them and see [1] for the full discussion.
Best,
Daniel
[1] https://github.com/mirage/ocaml-git/pull/130#issue-111278246
next reply other threads:[~2015-12-03 19:41 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-03 19:41 Daniel Bünzli [this message]
2015-12-04 17:03 ` Malcolm Matalka
2015-12-04 17:17 ` Daniel Bünzli
2015-12-04 17:23 ` Daniel Bünzli
2015-12-04 18:16 ` Malcolm Matalka
2015-12-04 18:30 ` Daniel Bünzli
2016-01-07 22:26 ` Daniel Bünzli
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=9FD64A9BC7C04CE0815129733504EE2E@erratique.ch \
--to=daniel.buenzli@erratique.ch \
--cc=caml-list@inria.fr \
--cc=drupyog@zoho.com \
--cc=mirageos-devel@lists.xenproject.org \
--cc=yallop@gmail.com \
/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