caml-list - the Caml user's mailing list
 help / color / mirror / Atom feed
From: "Jun Furuse" <jun.furuse@gmail.com>
To: "Nathaniel Gray" <n8gray@gmail.com>
Cc: caml-list@yquem.inria.fr
Subject: Re: [Caml-list] [ANN] OCamlSpotter: OCaml compiler extension for source browsing
Date: Tue, 9 Sep 2008 19:09:03 +0900	[thread overview]
Message-ID: <5160b4200809090309k2fe03206p3349038cebd36247@mail.gmail.com> (raw)
In-Reply-To: <aee06c9e0809082217j76e52f6ak2542ae9dac0a0810@mail.gmail.com>

Hi,

Of course, I've already expressed my hope of incorporating it into the
official compiler to the dev team.

But I think it is not the right moment. I am sure it has some bugs and
many things to be improved. Hopefully in future, when things become
more stable and if the dev team is convinced.

Cheers,
Jun

On Tue, Sep 9, 2008 at 2:17 PM, Nathaniel Gray <n8gray@gmail.com> wrote:
> On Mon, Sep 8, 2008 at 4:24 AM, Jun Furuse <jun.furuse@gmail.com> wrote:
>> Hi,
>>
>> I have written a small compiler patch called ocamlspotter. It extends
>> -annot option and records all the variable definition locations, so
>> that we can jump from variable uses to their definitions easily from
>> editors such as emacs.
>
> You have completely blown my mind.  I was thinking about this very
> idea about 10 minutes ago in my car, and *blam* there it is.  I should
> think about some other, more profitable ideas...
>
> I would suggest submitting this as a patch for inclusion.  I've heard
> there are going to be enhancements to the .annot format in 3.11 so
> it's not unprecedented.
>
> Cheers,
> -n8
>
> --
>>>>-- Nathaniel Gray -- Caltech Computer Science ------>
>>>>-- Mojave Project -- http://mojave.cs.caltech.edu -->
>


  reply	other threads:[~2008-09-09 10:09 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-09-08 11:24 Jun Furuse
2008-09-08 14:28 ` [Caml-list] " Jon Harrop
2008-09-08 20:43 ` Stefano Zacchiroli
2008-09-09  5:17 ` Nathaniel Gray
2008-09-09 10:09   ` Jun Furuse [this message]
2008-09-18 17:02   ` Xavier Leroy

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=5160b4200809090309k2fe03206p3349038cebd36247@mail.gmail.com \
    --to=jun.furuse@gmail.com \
    --cc=caml-list@yquem.inria.fr \
    --cc=n8gray@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).