From: Yoann Padioleau <padator@wanadoo.fr>
To: Jun Furuse <jun.furuse@gmail.com>
Cc: caml-list <caml-list@inria.fr>
Subject: Re: [Caml-list] OCamlSpotter for OCaml 3.12.0+rc1
Date: Sun, 25 Jul 2010 11:37:00 -0700 [thread overview]
Message-ID: <4E338414-66F6-4F69-8780-6B56F9D677A1@wanadoo.fr> (raw)
In-Reply-To: <AANLkTinnq_b++V0krXuP3Eihoctn9NYixJHxyXim56up@mail.gmail.com>
On Jul 23, 2010, at 11:29 PM, Jun Furuse wrote:
>
> Hi Caml-list,
>
> I have updated OCamlSpotter, a compiler enhancement for source code
> browsing, to version 3.12.0.0.0, which supports new syntax constructs
> introduced in OCaml 3.12.0+rc1. This is a very quick porting version
> for people who are already using OCamlSpotter with OCaml 3.11.2.
>
> OCamlSpotter is a tool which finds definition places of various names
> (identifiers, type names, modules, etc) in OCaml programs
> automatically for you. The original OCaml's -annot option provides the
> same sort of functionality
Really ? What is the difference between -annot and -dtypes. To me
-dtypes only help to print type information under the cursor (With C-c C-t).
It does not help to find the definition of a name (like otags).
> but OCamlSpotter provides much more
> powerful browsing: it can find definitions hidden in the deep nested
> module aliases and functor applications.
This looks really useful. Any chance of this being integrated in the official
OCaml distribution ? I don't feel comfortable overwriting my current
ocaml binaries. Also how does it interact with previously compiled object files ?
I am using godi so once I have overwritten the ocaml binaries from godi, do
I have to reinstall all the libraries ?
>
> - The -annot option of ocamlc and ocamlopt is extended and creates
> <module>.spot files (<module>.spit for .mli), which record the
> location information of the names defined and used in the module.
>
> - A small application ocamlspot provides automatic where-about
> spotting of the definition of the name you are interested in, using
> <module>.spot files created by the patched compilers.
>
> - ocamlspot.el provides interactive ocaml-spotting of definition
> locations in emacs.
>
> - Interfaces for other editors such as vi could be built easily, if you want.
>
> The source code is available from Mercurial repo at ocamlforge:
>
> Further information and download is available at:
>
> http://hg.ocamlcore.org/cgi-bin/hgwebdir.cgi/ocamlspotter/ocamlspotter/
>
> Documents are available currently at:
>
> http://jun.furuse.info/hacks/ocamlspotter
>
> which will be moved to ocamlforge soon.
>
> Happy hacking.
> Jun
>
> _______________________________________________
> Caml-list mailing list. Subscription management:
> http://yquem.inria.fr/cgi-bin/mailman/listinfo/caml-list
> Archives: http://caml.inria.fr
> Beginner's list: http://groups.yahoo.com/group/ocaml_beginners
> Bug reports: http://caml.inria.fr/bin/caml-bugs
>
next prev parent reply other threads:[~2010-07-25 18:37 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-24 6:29 Jun Furuse
2010-07-25 18:37 ` Yoann Padioleau [this message]
2010-07-26 14:10 ` [Caml-list] " Jun Furuse
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=4E338414-66F6-4F69-8780-6B56F9D677A1@wanadoo.fr \
--to=padator@wanadoo.fr \
--cc=caml-list@inria.fr \
--cc=jun.furuse@gmail.com \
/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).