caml-list - the Caml user's mailing list
 help / color / mirror / Atom feed
From: Jun Furuse <jun.furuse@gmail.com>
To: caml-list <caml-list@inria.fr>
Subject: [Caml-list] [ANN] OCamlOScope: a new OCaml API search
Date: Fri, 5 Jul 2013 10:11:55 +0800	[thread overview]
Message-ID: <CAAoLEWs9q6TSgeSm8qyp9Wa0tKVXDvwg0Ke3mp5kyDtaMcLUZg@mail.gmail.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 1451 bytes --]

Hi list,

I have launched a new OCaml API search, OCaml◎Scope at
http://ocamloscope.herokuapp.com .

OCaml◎Scope is a type directed library search, derived work from OCaml API
Search by Mizuno and its ancestor OCamlBrowser by Garrigue. It is also
inspired from Hoogle, the same API search engine for Haskell by MItchell,
which I regularly use in my Haskell :-) job.

* Fast and Portable. It loads everything in memory, unlike OCaml API Search
and OCamlBrowser which load compiled interface files (*.cmi) dynamically.
The data file is extracted from compiled files but self-contained, so the
search engine does not require to compile the libraries locally.
* No use of unification but edit distance of types like Hoogle. Unification
does not provide good results in type directed search, and is costy.
* OCamlFind and OPAM friendly. OCaml◎Scope knows which items are from which
OCamlFind and OPAM packages.
* OCamlDoc: it also extracts OCamlDoc comments, if possible.
* Small: it can even run as a heroku app. Currently it carries 245k entries
from 76 OCamlFind packages including Core and Batteries, but the data file
(as a marshalled OCaml value) is still 20Mb.

There are lots of todos but I think the search results look well sane so
far. If you find something strange please drop by
https://bitbucket.org/camlspotter/ocamloscope-server/issues?status=new&status=open
and
leave some comments. Thanks!

Jun Furuse

[-- Attachment #2: Type: text/html, Size: 1790 bytes --]

             reply	other threads:[~2013-07-05  2:11 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-07-05  2:11 Jun Furuse [this message]
2013-07-05  3:25 ` Yaron Minsky
2013-07-08 15:42   ` Jun Furuse
2013-07-05 14:51 ` Ashish Agarwal
2013-07-08 15:47   ` Jun Furuse
2013-07-08  0:51 ` Francois Berenger
2013-07-08 16:06   ` Jun Furuse
2013-07-08 18:58     ` Gerd Stolpmann

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=CAAoLEWs9q6TSgeSm8qyp9Wa0tKVXDvwg0Ke3mp5kyDtaMcLUZg@mail.gmail.com \
    --to=jun.furuse@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).