From: Jacques Garrigue <garrigue@math.nagoya-u.ac.jp>
To: mattias.waldau@abc.se
Cc: caml-list@yquem.inria.fr
Subject: Re: [Caml-list] How to refactor a large Ocaml program
Date: Fri, 15 Dec 2006 14:07:49 +0900 (JST) [thread overview]
Message-ID: <20061215.140749.85706043.garrigue@math.nagoya-u.ac.jp> (raw)
In-Reply-To: <458106BD.7060103@abc.se>
From: Mattias Waldau <mattias.waldau@abc.se>
> One problem with ocaml syntax is the open-statement, i.e. this makes it
> unclear for an editor
>
> Ocaml already has the -dtypes. Why doesn't this file contain information
> about where the functions and types are defined.
>
> For example, if you have a function call
>
> open Filename;
>
> let _ =
> concat .........
>
> in main.ml
>
> the main.annot contains
>
> "main.ml" 183 7050 7070 "main.ml" 183 7050 7085
> type(
> string -> string -> string
> )
>
> An improvement would be if it also contained information about the
> function, i.e.
>
> "main.ml" 183 7050 7070 "main.ml" 183 7050 7085
> type(
> Filename.concat: string -> string -> string
> )
>
> Then, the editor mode 'M-x goto-tag' or similar could look in the .annot
> file and open the correct file and go to the definition. (Maybe more
> information than Filename.concat is needed).
FYI, ocamlbrowser can already do that: open your file, typecheck it,
double-click on an identifier, and use the "impl" button in the type
browser.
It would not be much more difficult to do it in emacs, I suppose.
Jacques Garrigue
next prev parent reply other threads:[~2006-12-15 5:08 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
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 [this message]
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=20061215.140749.85706043.garrigue@math.nagoya-u.ac.jp \
--to=garrigue@math.nagoya-u.ac.jp \
--cc=caml-list@yquem.inria.fr \
--cc=mattias.waldau@abc.se \
/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