caml-list - the Caml user's mailing list
 help / color / mirror / Atom feed
From: Yaron Minsky <yminsky@gmail.com>
To: Alp Mestan <alp@mestan.fr>
Cc: Andrej Bauer <andrej.bauer@andrej.com>, caml-list@yquem.inria.fr
Subject: Re: [Caml-list] Improving OCaml's choice of type to display
Date: Fri, 9 Oct 2009 07:15:00 -0400	[thread overview]
Message-ID: <891bd3390910090415r1d2d43f1q71a8da2df741678d@mail.gmail.com> (raw)
In-Reply-To: <cbe39dfc0910090354t6439f9et385eb66ea92ed0a5@mail.gmail.com>

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

On Fri, Oct 9, 2009 at 6:54 AM, Alp Mestan <alp@mestan.fr> wrote:

> Can't there be a trick by playing with, e.g, ocamlmktop, which could open
> Core and its main submodules by default, like it's done with Pervasives and,
> IIRC, Batteries ?
>

Maybe.  Although to be honest my main concern is not with the top-level, but
rather with the errors given out by ocamlc, and the type-inference hints
given by the -dtypes flag.  The naming choices are easiest to see in the
toplevel, but they show up all over the place.

y


> On Fri, Oct 9, 2009 at 11:58 AM, Yaron Minsky <yminsky@gmail.com> wrote:
>
>> Well, if we're picking heuristics, the fewest number of characters
>> wouldn't be crazy either.  Given the choice between Int.t and Int.comparable
>> (which are aliases for the same type), I'd prefer to see Int.t.
>>
>> y
>>
>>
>> On Fri, Oct 9, 2009 at 3:33 AM, Andrej Bauer <andrej.bauer@andrej.com>wrote:
>>
>>> On Fri, Oct 9, 2009 at 3:40 AM, Yaron Minsky <yminsky@gmail.com> wrote:
>>> > Choosing shorter names.
>>>
>>> By which you probably mean "the fewest number of dots (module
>>> projections)". It might be a bit annoying if the code that prints
>>> doesn't know what modules are open. What do the INRIA priests say?
>>>
>>> Andrej
>>>
>>
>>
>> _______________________________________________
>> Caml-list mailing list. Subscription management:
>> http://yquem.inria.fr/cgi-bin/mailman/listinfo/caml-list
>> Archives: http://caml.inria.fr
>> Beginner's list: http://groups.yahoo.com/group/ocaml_beginners
>> Bug reports: http://caml.inria.fr/bin/caml-bugs
>>
>>
>
>
> --
> Alp Mestan
> http://alpmestan.wordpress.com/
> http://alp.developpez.com/
>

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

  reply	other threads:[~2009-10-09 11:15 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-10-09  1:40 Yaron Minsky
2009-10-09  1:53 ` Yaron Minsky
2009-10-11 14:57   ` [Caml-list] " Jun Furuse
2009-10-11 15:12     ` Yaron Minsky
2009-10-11 15:24       ` Jun Furuse
2009-10-11 19:57         ` Gilles Pirio
2009-10-11 21:17           ` [Caml-list] " Damien Guichard
2009-10-11 21:46             ` Gilles Pirio
2009-10-11 22:16               ` Lukasz Stafiniak
2009-10-09  7:33 ` Andrej Bauer
2009-10-09  9:58   ` Yaron Minsky
2009-10-09 10:54     ` Alp Mestan
2009-10-09 11:15       ` Yaron Minsky [this message]
2009-10-09 14:18     ` Damien Guichard
2009-10-09 14:44       ` Vincent Aravantinos
2009-10-09 15:27         ` David Allsopp
2009-10-09 16:52       ` Yaron Minsky
2009-10-09 18:23         ` Damien Guichard
2009-10-09 18:14   ` Stephen Weeks
2009-10-10 15:08     ` Damien Guichard

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=891bd3390910090415r1d2d43f1q71a8da2df741678d@mail.gmail.com \
    --to=yminsky@gmail.com \
    --cc=alp@mestan.fr \
    --cc=andrej.bauer@andrej.com \
    --cc=caml-list@yquem.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).