caml-list - the Caml user's mailing list
 help / color / mirror / Atom feed
From: "Nathaniel Gray" <n8gray@gmail.com>
To: "Xavier Leroy" <Xavier.Leroy@inria.fr>
Cc: "Jun Furuse" <jun.furuse@gmail.com>, caml-list@yquem.inria.fr
Subject: Extending .annot files
Date: Fri, 19 Sep 2008 11:20:36 -0700	[thread overview]
Message-ID: <aee06c9e0809191120i33409998i8335e7f5392b92b1@mail.gmail.com> (raw)

On Thu, Sep 18, 2008 at 10:02 AM, Xavier Leroy <Xavier.Leroy@inria.fr> wrote:
>
> From what I've heard, there's also an OCaml summer of code project
> that enriched the info found in .annot files.  So, it's certainly time
> to discuss extensions to .annot files, but let's do that globally, not
> one at a time.  It is probably too late for inclusion in 3.11, but as
> long as these extensions are backward compatible, inclusion in bugfix
> releases can be considered.

I'm really happy to hear that you're open to including some of this
stuff.  I think there are actually only a few data that one wants to
have in .annot files (and that the compiler can reasonably provide).

For any identifier it would be good to know:
1. Its inferred type
2. Its fully-qualified module "path"
3. Where it was defined, if it was defined in the current file.

In addition, for each module referenced in the file it would be good
to know what file the module was read from.  (This will allow some
hope of tracking down definitions in other files)

It's hard for me to think of anything else that belongs in .annot
files.  If I stretch a bit I suppose annotating variable definitions
with their range of scope might be cute.  Maybe other people can think
of more original ideas.

Finally, it may be worth putting a little work into reducing the size
of .annot files.  One could certainly do much better with very little
effort.

Cheers,
-n8

-- 
>>>-- Nathaniel Gray -- Caltech Computer Science ------>
>>>-- Mojave Project -- http://mojave.cs.caltech.edu -->


             reply	other threads:[~2008-09-19 18:20 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-09-19 18:20 Nathaniel Gray [this message]
2008-09-22  2:15 ` Jun Furuse
2008-09-24  7:33   ` [Caml-list] " Nathaniel Gray
2008-09-24 16:19     ` Jun Furuse
2008-09-22  6:08 ` [Caml-list] " Maxence Guesdon
2008-09-24  7:50   ` Nathaniel Gray

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