From: David Baelde <david.baelde@gmail.com>
To: yoann padioleau <aryx.padator@gmail.com>
Cc: "Arnaud Spiwack" <aspiwack@lix.polytechnique.fr>,
"Daniel Bünzli" <daniel.buenzli@erratique.ch>,
"caml users" <caml-list@inria.fr>
Subject: Re: [Caml-list] Detecting dead code, discovering a project's structure...
Date: Thu, 5 Feb 2015 21:52:22 +0100 [thread overview]
Message-ID: <CAFqqUFFsKQY9_wdvddjpO=Oa8Ls3qjRrLB_ud1AzwscPdfvBdw@mail.gmail.com> (raw)
In-Reply-To: <990B49F8-A93F-491F-9421-02BF480FE429@gmail.com>
Hi Sebastien and everybody,
Another (late, but maybe useful) suggestion is to look at bisect:
http://bisect.x9c.fr/
It's not a static analysis but a coverage checker. Still, it'll show
you entry points, and also dead code, on some example runs. I've tried
it recently (on a medium pure OCaml tool) and found it surprisingly
easy to use.
Cheers,
David
On Thu, Jan 29, 2015 at 7:24 AM, yoann padioleau <aryx.padator@gmail.com> wrote:
> Yes in the configure script cmt is enabled only for
> certain ocaml versions.
> The problem is that the caml AST format (stored in the .cmt) has changed in
> every versions … I would have hoped for a more
> stable type.
>
> #TODO: not yet ported to 4.02
> if($ocaml_version >= 4000 && $ocaml_version < 4020) {
> $cmt=1;
>
>
> On Jan 23, 2015, at 6:52 AM, Arnaud Spiwack <aspiwack@lix.polytechnique.fr>
> wrote:
>
> No, I actually just downloaded the sources and compiled them. Maybe it's
> because I compiled pfff with ocaml 4.02.1, I notice there isn't a package
> for pfff in the corresponding opam switch. I'll have to try other versions.
>
> On 23 January 2015 at 15:26, Daniel Bünzli <daniel.buenzli@erratique.ch>
> wrote:
>>
>>
>>
>> Le vendredi, 23 janvier 2015 à 15:02, Arnaud Spiwack a écrit :
>>
>> > I'm confused. I've got a version of pfff compiled from today's github
>> > version. I get the following:
>> >
>> > $ codegraph -lang cmt -build .
>> > Fatal error: exception Failure("language not supported: cmt")
>>
>> Did you get it by pinning opam ? This may explain:
>>
>>
>> https://github.com/ocaml/opam-repository/blob/master/packages/pfff/pfff.0.27.3/opam#L5
>>
>> Best,
>>
>> Daniel
>>
>>
>>
>
>
--
David
next prev parent reply other threads:[~2015-02-05 20:52 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-08 13:31 Sébastien Hinderer
2015-01-08 13:48 ` Stéphane Glondu
2015-01-08 13:54 ` Sébastien Hinderer
2015-01-08 15:33 ` Goswin von Brederlow
2015-01-08 15:50 ` Ashish Agarwal
2015-01-15 18:16 ` yoann padioleau
2015-01-19 9:58 ` Arnaud Spiwack
2015-01-22 21:09 ` yoann padioleau
2015-01-23 14:02 ` Arnaud Spiwack
2015-01-23 14:26 ` Daniel Bünzli
2015-01-23 14:52 ` Arnaud Spiwack
2015-01-29 6:24 ` yoann padioleau
2015-02-05 20:52 ` David Baelde [this message]
2015-01-08 15:50 ` Jeremy Yallop
2015-01-08 14:03 ` Sébastien Hinderer
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='CAFqqUFFsKQY9_wdvddjpO=Oa8Ls3qjRrLB_ud1AzwscPdfvBdw@mail.gmail.com' \
--to=david.baelde@gmail.com \
--cc=aryx.padator@gmail.com \
--cc=aspiwack@lix.polytechnique.fr \
--cc=caml-list@inria.fr \
--cc=daniel.buenzli@erratique.ch \
/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).