From: oliver <oliver@first.in-berlin.de>
To: Pierre-Yves Strub <pierre-yves@strub.nu>
Cc: caml-list@inria.fr
Subject: Re: [Caml-list] Dead code detection
Date: Wed, 11 Dec 2013 17:46:53 +0100 [thread overview]
Message-ID: <20131211164653.GA1937@siouxsie> (raw)
In-Reply-To: <a6230abe4852ccaee38d2cd206495b58@strub.nu>
Hello,
On Wed, Dec 11, 2013 at 03:52:54PM +0100, Pierre-Yves Strub wrote:
> Hi all,
>
> Does any of you know a tool for doing dead code detection?
[...]
-w flags for
suspicious comment
partially applied function
overriden methods
non-unit statement
overriden instance variables
* suspicious unused variables
* all other unused variables
Especially unused variables may show lurking code,
that was once written in an intermediate state of
code development, and never be used again since then.
Ciao,
Oliver
next prev parent reply other threads:[~2013-12-11 16:46 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-11 14:52 Pierre-Yves Strub
2013-12-11 14:56 ` Simon Cruanes
2013-12-11 14:56 ` Fabien Renaud
2013-12-11 15:07 ` Alain Frisch
2013-12-11 16:46 ` oliver [this message]
2013-12-11 21:18 ` Yoann Padioleau
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=20131211164653.GA1937@siouxsie \
--to=oliver@first.in-berlin.de \
--cc=caml-list@inria.fr \
--cc=pierre-yves@strub.nu \
/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