[
Home
]
[ Index:
by date
|
by threads
]
[ Message by date: previous | next ] [ Message in thread: previous | next ] [ Thread: previous | next ]
[ Message by date: previous | next ] [ Message in thread: previous | next ] [ Thread: previous | next ]
Date: | 2010-07-26 (14:10) |
From: | Jun Furuse <jun.furuse@g...> |
Subject: | Re: [Caml-list] OCamlSpotter for OCaml 3.12.0+rc1 |
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