caml-list - the Caml user's mailing list
 help / color / mirror / Atom feed
From: Yotam Barnoy <yotambarnoy@gmail.com>
To: Ocaml Mailing List <caml-list@inria.fr>
Subject: [Caml-list] Ocaml compiler documentation
Date: Mon, 31 Mar 2014 11:39:21 -0400	[thread overview]
Message-ID: <CAN6ygOnF4oz6+bWhz_S-ZybLoyzySnQkN8Z-5ggj2RS-5PrKKw@mail.gmail.com> (raw)

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

Hi everybody

It's been mentioned before that the OCaml compiler's documentation is
somewhat lacking. I've been going over the compiler code gradually (both
the frontend and the backend) and while some parts are understandable
enough, others are missing some basic explanations. Some explanations are
also spread out throughout the codebase, making it hard to know what
something means unless you've read another part of the codebase that
relates to it.

Since the call to submit documentation commits has gone mostly unanswered,
I'd like to suggest a method of making both my own progress through the
code easier and hopefully making it easier for others who will follow.

What I'm going to do is, focusing on more or less one file at a time, I'll
post newbie questions to the list about the code. Once I'm satisfied that I
have a good enough understanding, I'll add comments to the aforementioned
files and submit pull requests for them. I also encourage others to do the
same.

What I need from the list, and especially from the more knowledgeable
members (who already know the compiler code) is the willingness to explain
the concepts and answer my questions, annoying as they may be. I have a
pretty decent background in compilers, ASTs, code generation, etc, but not
so much in type inference.

I'm not suggesting a particular timeframe for this process -- I'm doing
this on the side while working on a research project and TAing, but I
really would like to get to the point where I can make significant
contributions to the toolchain, and if I can help others who follow in my
footsteps, then that's a nice bonus.

While I could have skipped this introduction and just proceeded with
inundating the list with questions, I felt that this (hopefully) gives a
purpose and perhaps motivation for those who have the answers to answer my
questions even if they get annoying. In particular, I may often miss some
parts that may seem obvious because I don't necessarily have the time to
read all the connected code in depth. Hopefully you'll bear with me.

Does this sound reasonable to the fine folks on the list?

Yotam

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

             reply	other threads:[~2014-03-31 15:39 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-03-31 15:39 Yotam Barnoy [this message]
2014-03-31 17:06 ` Milan Stanojević
2014-03-31 17:51   ` Yotam Barnoy
2014-04-01 10:03     ` Mark Shinwell
2014-04-03  2:48       ` Yotam Barnoy
2014-04-03  6:18         ` Mark Shinwell
2014-04-03  8:42         ` Jeremy Yallop
2014-04-03  9:05         ` David Allsopp
2014-04-03 10:20           ` Simon Cruanes
2014-04-03 10:46             ` David Allsopp
2014-04-03 18:17               ` Yotam Barnoy
2014-04-03  9:10         ` Gabriel Scherer
2014-04-03 20:16         ` Alain Frisch
2014-04-04  7:39           ` François Bobot
2014-04-14  6:12           ` Mark Shinwell
2014-04-14  7:44             ` Alain Frisch

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=CAN6ygOnF4oz6+bWhz_S-ZybLoyzySnQkN8Z-5ggj2RS-5PrKKw@mail.gmail.com \
    --to=yotambarnoy@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).