From: "Sébastien Hinderer" <Sebastien.Hinderer@inria.fr>
To: caml-list@inria.fr
Subject: [Caml-list] Detecting dead code, discovering a project's structure...
Date: Thu, 8 Jan 2015 14:31:11 +0100 [thread overview]
Message-ID: <20150108133111.GA3745@pl-59055.rocqadm.inria.fr> (raw)
Dear all,
Are there tools / techniques one could use to make it easier to
discover / explore the source code of a big OCaml project?
In particular, are there any tools available to help finding dead code
or coe that may need some refactoring?
Many thanks for any suggestion.
Sébastien.
next reply other threads:[~2015-01-08 13:30 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-08 13:31 Sébastien Hinderer [this message]
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
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=20150108133111.GA3745@pl-59055.rocqadm.inria.fr \
--to=sebastien.hinderer@inria.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).