From: Jun Furuse <jun.furuse@gmail.com>
To: Yoann Padioleau <padator@wanadoo.fr>
Cc: caml-list <caml-list@inria.fr>
Subject: Re: [Caml-list] OCamlSpotter for OCaml 3.12.0+rc1
Date: Mon, 26 Jul 2010 23:10:55 +0900 [thread overview]
Message-ID: <AANLkTi=jRuvYSO1635XCRT9p+NBMXsOUcqVAWu6qVLjM@mail.gmail.com> (raw)
In-Reply-To: <4E338414-66F6-4F69-8780-6B56F9D677A1@wanadoo.fr>
Hi,
> 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).
No difference. -dtype was superseded by -annot while ago. OCamlSpotter
extends these options to produce extra files for code browsing.
>> 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 patch does not touch any part of compilation, or at least I was
careful to keep the compilation part untouched. This means patched
compiler and the orignal should produce the same object codes. It
should be safe linking of objects from the original and the patched
together, as far as you use the same compiler versions. Of course,
there are no spot/spit files for library modules compiled by the
original compiler and you cannot browse them.
If you want to be very careful, use the patched compiler just for
spot/spit file creation and use the object files from the original
compiler. In this case you need to tweak your build scripts (Makefile,
OMakefile, ocamlbuild or whatever) somehow. Probably I can add
-annotonly option for the next version of OCamlSpotter to make it
easier.
I am not sure about the possibility of official integration of the
patch. Caml-dev team is generally conservative for a good reason: they
are responsible for keeping ocaml maintenable by themselves.
OCamlSpotter was made based on some non-trivial (probably wrong)
design choices. Maybe some people find OCamlWizard
(http://ocamlwizard.lri.fr/) is better. Or others like pretty heavy
weight solutions like Scion server for Haskell.
Jun
prev parent reply other threads:[~2010-07-26 14:10 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 ` [Caml-list] " Yoann Padioleau
2010-07-26 14:10 ` Jun Furuse [this message]
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='AANLkTi=jRuvYSO1635XCRT9p+NBMXsOUcqVAWu6qVLjM@mail.gmail.com' \
--to=jun.furuse@gmail.com \
--cc=caml-list@inria.fr \
--cc=padator@wanadoo.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).