caml-list - the Caml user's mailing list
 help / color / mirror / Atom feed
From: Judicael.Courant@lip.ens-lyon.fr (Judicael Courant)
To: caml-list@pauillac.inria.fr
Subject: Dead code removal / cross references
Date: Thu, 10 Nov 94 09:11:51 +0100	[thread overview]
Message-ID: <9411100811.AA02292@lip.ens-lyon.fr> (raw)

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 1057 bytes --]

Bonjour,

travaillant sur un projet en camllight assez imposant (plus de 170
fichiers .ml), j'aimerais disposer d'outils permettant d'avoir des
références croisées (ou est définie telle fonction ? ou est appelée
telle fonction ? quels modules sont utilisés par tel module ? ce #open
est-il bien nécessaire ?), et permettant de détecter et d'éliminer lés
#open inutiles et le code mort (relativement a un ou des fichiers
donnés). De tels outils existent-ils ?

Merci.

--------------------------------------

Hello,

working on a quite large project written in camllight (more than 170
.ml files), I would like to have a tool that would generate some
cross-references (where is this function/type defined ? where is it
called/used ? which modules are used by this one ? is this #open
really necessary ?) and detect and remove the useless #open and the
dead code. Does such a tool exists ?

Thanks.

-- 
Judicaël COURANT           tel. : 72 72 85 82
ENSL - LIP                 email : Judicael.Courant@ens-lyon.fr
46, allée d'Italie
69364 Lyon cedex 07
--




             reply	other threads:[~1994-11-10 15:24 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1994-11-10  8:11 Judicael Courant [this message]
1994-11-14 10:38 ` Xavier Leroy
1994-11-11 19:18 Doug Currie, Flavors Technology, Inc.

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=9411100811.AA02292@lip.ens-lyon.fr \
    --to=judicael.courant@lip.ens-lyon.fr \
    --cc=caml-list@pauillac.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).