caml-list - the Caml user's mailing list
 help / color / mirror / Atom feed
From: Anton Bachin <antronbachin@gmail.com>
To: OCaml Mailing List <caml-list@inria.fr>
Subject: Re: [Caml-list] Bisect_ppx: removing report output formats, etc.
Date: Fri, 10 Jun 2016 09:08:25 -0500	[thread overview]
Message-ID: <1837176F-6E06-4179-B532-3E7E6636509E@gmail.com> (raw)
In-Reply-To: <27190B91-13B2-4DB6-8794-F72BCB3E9C64@gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1160 bytes --]

I would like to clarify that -combine-expr is not about combining multiple output files as in

  bisect-ppx-report -html report *.out

That is not being removed.

-combine-expr is a separate feature that allows visitation counts of two or more separate sets of *.out files to be manipulated, for example by subtracting them, to obtain a new report.

Best,
Anton

> On Jun 10, 2016, at 08:46, Anton Bachin <antronbachin@gmail.com> wrote:
> 
> Hello,
> 
> We are in the process of removing the following features from Bisect_ppx, as we don’t believe they are used:
> 
> - combine expressions (reporter’s -combine-expr)
> - XML output
> - EMMA output
> - “bisect” output [1]
> - point kinds (mentioned earlier [2])
> 
> We would also like to remove “dump” output, but we are using it internally for testing.
> 
> Please let me know of any objections.
> 
> Best,
> Anton
> 
> 
> [1]: https://github.com/aantron/bisect_ppx/pull/106 <https://github.com/aantron/bisect_ppx/pull/106>
> [2]: https://sympa.inria.fr/sympa/arc/caml-list/2016-06/msg00004.html <https://sympa.inria.fr/sympa/arc/caml-list/2016-06/msg00004.html>

[-- Attachment #2: Type: text/html, Size: 2451 bytes --]

      reply	other threads:[~2016-06-10 14:08 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-06-10 13:46 Anton Bachin
2016-06-10 14:08 ` Anton Bachin [this message]

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=1837176F-6E06-4179-B532-3E7E6636509E@gmail.com \
    --to=antronbachin@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;
as well as URLs for NNTP newsgroup(s).