From: "Lukasz Stafiniak" <lukstafi@gmail.com>
To: caml <caml-list@inria.fr>
Subject: Postulates for OCaml Development Environment (under Emacs)
Date: Wed, 14 Mar 2007 18:10:50 +0100 [thread overview]
Message-ID: <4a708d20703141010x54fffb3bve4bb1f1eaa214e85@mail.gmail.com> (raw)
I propose some brain-storming on IDE issues.
1. Parse with Camlp4 for all functionality: indentation and Emacs Code
Browser-like features. Augmented with information from .annot files.
2. Use heuristics to repair unfinished code, like here (example should
be better, I'm sorry):
replace in the background (not in the buffer)
let rec fib n = if then 1 else fib(n-1) +
;;
with
let x01 = ref None;;
let x02 = ref None;;
let f01() = match !x01 with Some x -> x | None -> failwith "x01";;
let f02() = match !x02 with Some x -> x | None -> failwith "x02";;
let rec fib n = if (f01()) then 1 else fib(n-1) + (f02());;
Report types for unfinished code as well with C-c C-t.
3. Follow-to-definition and show-where-used for identifiers.
4. Customize `allout-mode' to use ocamldoc syntax.
5. Did I mention context-aware complete? Based on the AST returned by
Camlp4 together with .annot files. Perhaps unifying types to get a
clean list of candidates.
Best Regards,
Lukasz
reply other threads:[~2007-03-14 17:10 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=4a708d20703141010x54fffb3bve4bb1f1eaa214e85@mail.gmail.com \
--to=lukstafi@gmail.com \
--cc=caml-list@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).