You first days after joining a large OCaml project should be this kind
of manual value definition spotting with find + grep commands. Yes,
actually it is very educational: you can learn a lot about the project
-struggling in the source tree (only if your collegues have organized
+struggling in the source tree (only if your collegues have organized
things very well :-P), but it is still a dull job...
To say short, OCamlSpotter is a tool which does this dull job
Retrieve various annotation information from .spot or .spit files
of the source code position or identifier, specified by the
- search spec. Information is prited to stdout. They are:
+ search spec. Information is prited to stdout. They are:
The definition position of the object which the search spec
The type of the object which the search spec points to, if
available. In XType, paths are printed with position
iton: for example, "unit__6" instead of "unit".
+ informaton: for example, "unit__6" instead of "unit".
The kind and the name with id numbers of the identifier
+Value usage analysis (Experimental)
+ ocamlspot use [search] [target files and dirs]
+ search ::= [file]:[pos] | [file]:[kind]:[path]
+ pos ::= l[line]c[column_bytes] | b[bytes] | [bytes]
+ kind ::= v|t|e|m|mt|c|ct
+ ocamlspot use does opposite of ocamlspot query: search the uses of
+ the identifier specified by the search spec.
+ After the search spec, the search target path names can be specified.
+ If a target is a directory, the search is performed recursively
Spot creation w/o real compilation
.annot/.spot/.spit files using the compilation information already
stored in .spot/.spit files.
+ocamlspot.el emacs interface