From: Jon Harrop <jon@ffconsultancy.com>
To: caml-list@yquem.inria.fr
Subject: Re: [Caml-list] How to refactor a large Ocaml program
Date: Wed, 13 Dec 2006 14:09:24 +0000 [thread overview]
Message-ID: <200612131409.24433.jon@ffconsultancy.com> (raw)
In-Reply-To: <4580079B.1020101@trusted-logic.fr>
On Wednesday 13 December 2006 14:00, Yann Coscoy wrote:
> And if these tools do not exists it is not because nobody need nor want
> them. It is because it requires a huge effort to have good ones. And
> nobody has done is effort yet.
I don't think it would be a huge effort to write refactoring tools for OCaml.
Indeed, I've propose this idea for F#. The hard part is writing the lexer and
parser, which is already found in the front end of the compiler (albeit
without parsing of comments). Then you're just rewriting an AST, which is a
piece of cake in ML. :-)
--
Dr Jon D Harrop, Flying Frog Consultancy Ltd.
Objective CAML for Scientists
http://www.ffconsultancy.com/products/ocaml_for_scientists
next prev parent reply other threads:[~2006-12-13 14:12 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 [this message]
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
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=200612131409.24433.jon@ffconsultancy.com \
--to=jon@ffconsultancy.com \
--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).