caml-list - the Caml user's mailing list
 help / color / mirror / Atom feed
From: Bruno De Fraine <Bruno.De.Fraine@vub.ac.be>
To: caml-list@yquem.inria.fr
Subject: Re: [Caml-list] How to refactor a large Ocaml program
Date: Thu, 14 Dec 2006 12:59:43 +0100	[thread overview]
Message-ID: <82A46954-1B75-4966-B6B3-F93A0DA21001@vub.ac.be> (raw)
In-Reply-To: <458106BD.7060103@abc.se>

Hello,

I think there are a number of factors that certainly make it easier  
to develop refactoring tools for Ocaml:
- it is a static language
- there is already source code available for working with Ocaml code,  
e.g. ocamlc

> Ocaml already has the -dtypes. Why doesn't this file contain  
> information about where the functions and types are defined.

Yes, it seems like a good idea for ocamlc to emit defines/uses  
annotations, at least for lowercase identifiers in the syntax tree.  
For example, if I show these annotations in-place as comments:

let foo(* defines: _global01 *) = 12 ;;
let bar(* defines: _global02 *) x(* defines: _local01 *) =
	foo(* uses: _global01 *) + x(* uses: _local01 *) ;;
bar(* uses: _global02 *) foo(* uses: _global01 *) ;;
let foo(* defines: _global03 *) = "foo" ;;
(* etc. *)

Your editor would be able to jump from definition to usage and vice  
versa with this information.

Editing and recompiling is what we currently use to discover this  
information mechanically, but it seems better not to have to make  
destructive changes to source files.

Bye,
Bruno

-- 
Bruno De Fraine
Vrije Universiteit Brussel
Faculty of Applied Sciences, INFO - SSEL
Room 4K208, Pleinlaan 2, B-1050 Brussels
tel: +32 (0)2 629 29 75
fax: +32 (0)2 629 28 70
e-mail: Bruno.De.Fraine@vub.ac.be


  reply	other threads:[~2006-12-14 11:59 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-12-13 12:37 Mattias Waldau
2006-12-13 13:09 ` [Caml-list] " Pietro Abate
2006-12-13 13:46   ` Jon Harrop
2006-12-13 13:53   ` skaller
2006-12-13 13:57   ` Richard Jones
2006-12-13 14:00   ` Yann Coscoy
2006-12-13 14:09     ` Jon Harrop
2006-12-13 14:31       ` Yann Coscoy
2006-12-13 14:42       ` Mattias Engdegård
2006-12-13 16:48     ` Gerd Stolpmann
2006-12-13 17:08       ` Jon Harrop
2006-12-13 13:51 ` Jim Miller
     [not found] ` <45800CD5.8050401@janestcapital.com>
2006-12-14  8:09   ` Mattias Waldau
2006-12-14 11:59     ` Bruno De Fraine [this message]
2006-12-14 13:47     ` Brian Hurt
2006-12-15 15:33       ` Florian Hars
2006-12-16 10:14         ` Remi Vanicat
2006-12-16 13:53           ` Christian Stork
2006-12-18 19:37           ` Florian Hars
2006-12-15  5:07     ` Jacques Garrigue
2006-12-15  7:49       ` Mattias Waldau
2006-12-15 12:36         ` Jan Rehders
2006-12-15 13:11           ` skaller
2006-12-14  8:21   ` Mattias Waldau
2006-12-15 17:23 ` malc

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=82A46954-1B75-4966-B6B3-F93A0DA21001@vub.ac.be \
    --to=bruno.de.fraine@vub.ac.be \
    --cc=caml-list@yquem.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).