caml-list - the Caml user's mailing list
 help / color / mirror / Atom feed
From: Jeremy Yallop <yallop@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 15:50:41 +0000	[thread overview]
Message-ID: <CAAxsn=E03QOXuJD1UqfnHSeUy-8VAu8HgieUmQAcYpSnj5mr4w@mail.gmail.com> (raw)
In-Reply-To: <20150108153342.GB4890@frosties>

On 8 January 2015 at 15:33, Goswin von Brederlow <goswin-v-b@web.de> wrote:
> Similar for types / values defined but not used in .ml files that do
> not appear in the .mli file.

OCaml can warn for these already:

  $ cat unused.mli
  type t
  val x : t

  $ cat unused.ml
  type t = int
  type s = int
  let x = 3
  let y = 4

  $ ocamlc -w A unused.mli unused.ml
  File "unused.ml", line 2, characters 5-12:
  Warning 34: unused type s.
  File "unused.ml", line 4, characters 4-5:
  Warning 32: unused value y.

  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
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 [this message]
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='CAAxsn=E03QOXuJD1UqfnHSeUy-8VAu8HgieUmQAcYpSnj5mr4w@mail.gmail.com' \
    --to=yallop@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).