Mailing list for all users of the OCaml language and system.
 help / color / mirror / Atom feed
From: Siraaj Khandkar <siraaj@khandkar.net>
To: David MENTRE <dmentre@linux-france.org>,
	 Paolo Donadeo <p.donadeo@gmail.com>
Cc: OCaml mailing list <caml-list@inria.fr>
Subject: Re: [Caml-list] UFO (United Forces of OCaml)
Date: Fri, 27 Sep 2013 12:25:17 -0400	[thread overview]
Message-ID: <5245B16D.9090101@khandkar.net> (raw)
In-Reply-To: <CAC3Lx=Z+peti1nEoJbh0kp2WdB_iMnvhjLfbv9mwoYBcSOeO9A@mail.gmail.com>

On 09/27/2013 11:55 AM, David MENTRE wrote:
> Hello,
>
> 2013/9/27 Paolo Donadeo <p.donadeo@gmail.com>:
>> But, regarding the specific case of the
>> "extended library", there aren't many libraries, but only two:
>> Batteries and Core. And I think both of them have very strong points,
>> and the design is quite different.
>
> Is there a short document somewhere explaining those design differences?
>

I haven't seen a document comparing the goals of both directly, but 
individually each project stated differing goals:

- Batteries aims to be a compatible _extension_ of stdlib (so minimal or 
no changes required for code already using stdlib)

- Core is an incompatible _replacement_ for stdlib, aiming to take the 
greatest advantage of the type system (existing code would have to be 
updated to use Core's API)

  reply	other threads:[~2013-09-27 16:25 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-09-27  7:11 Gour
2013-09-27 11:20 ` Török Edwin
2013-09-27 12:04   ` Yaron Minsky
2013-09-27 12:15     ` Paolo Donadeo
2013-09-27 15:55       ` David MENTRE
2013-09-27 16:25         ` Siraaj Khandkar [this message]
2013-09-27 16:45           ` Ashish Agarwal
2013-09-27 12:13   ` Gour
2013-09-27 11:25 ` Lukasz Stafiniak
2013-09-30  1:40 ` Francois Berenger
2013-09-30  6:01   ` Gour
2013-09-30  6:33     ` Francois Berenger
2013-09-30 14:14   ` Sylvain Le Gall
2013-09-27 17:08 Damien Guichard
2013-09-27 18:58 ` Gour

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=5245B16D.9090101@khandkar.net \
    --to=siraaj@khandkar.net \
    --cc=caml-list@inria.fr \
    --cc=dmentre@linux-france.org \
    --cc=p.donadeo@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