From: Ashish Agarwal <agarwal1975@gmail.com>
To: Goswin von Brederlow <goswin-v-b@web.de>
Cc: Caml List <caml-list@inria.fr>
Subject: Re: [Caml-list] Detecting dead code, discovering a project's structure...
Date: Thu, 8 Jan 2015 10:50:27 -0500 [thread overview]
Message-ID: <CAMu2m2KhKfcWdWD1x1EzoBkDkCaa0f08CsGPbJX5c77UgawnWQ@mail.gmail.com> (raw)
In-Reply-To: <20150108153342.GB4890@frosties>
[-- Attachment #1: Type: text/plain, Size: 1509 bytes --]
Maybe Pfff:
https://github.com/facebook/pfff
On Thu, Jan 8, 2015 at 10:33 AM, Goswin von Brederlow <goswin-v-b@web.de>
wrote:
> On Thu, Jan 08, 2015 at 02:48:12PM +0100, Stéphane Glondu wrote:
> > Le 08/01/2015 14:31, Sébastien Hinderer a écrit :
> > > 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.
> >
> > One suggestion: http://home.gna.org/oug/index.fr.html
> >
> >
> > Cheers,
>
> That looks cool. But that still needs a lot of manual filtering to get
> results, e.g. to find an unused type or function specified in the
> input signature for a functor.
>
> It could be nice for ocaml to have warnings for this directly. E.g.:
>
> module type M = ssig type t type s val x : int end
> moduel F(M : M) = struct type t = M.t end
>
> Warning: unused value x in signature M for functor F
> Warning: unused type s in signature M for functor F
>
> Similar for types / values defined but not used in .ml files that do
> not appear in the .mli file.
>
> MfG
> Goswin
>
> --
> Caml-list mailing list. Subscription management and archives:
> https://sympa.inria.fr/sympa/arc/caml-list
> Beginner's list: http://groups.yahoo.com/group/ocaml_beginners
> Bug reports: http://caml.inria.fr/bin/caml-bugs
>
[-- Attachment #2: Type: text/html, Size: 2415 bytes --]
next prev parent reply other threads:[~2015-01-08 15:50 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 [this message]
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=CAMu2m2KhKfcWdWD1x1EzoBkDkCaa0f08CsGPbJX5c77UgawnWQ@mail.gmail.com \
--to=agarwal1975@gmail.com \
--cc=caml-list@inria.fr \
--cc=goswin-v-b@web.de \
/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).