caml-list - the Caml user's mailing list
 help / color / mirror / Atom feed
From: Fabrice Le Fessant <Fabrice.Le_fessant@inria.fr>
To: caml-list@inria.fr
Subject: Re: [Caml-list] [ANN] Argot: 1.0 release
Date: Fri, 04 Nov 2011 10:55:53 +0100	[thread overview]
Message-ID: <4EB3B6A9.7090506@inria.fr> (raw)
In-Reply-To: <20111104092409.GA22221@ccellier.rd.securactive.lan>

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

> Also, apparently one cannot search by type. It would be a nice feature
> to have.

Thomas, add it to the features list ! ;-)

> Last thing, unrelated: from the search box one can see you have many
> modules extending the stdlib (the Ocp* modules). Why another stdlib
> extension instead of, say, contributing to batteries ?

First, we don't have so many of them, we only put there what we needed
for our set of tools. Some of them are really close to the compiler, and
we might submit them for inclusion in the official distribution, so we
didn't want to add a dependency to Batteries or Core too early.

The other reason is that we haven't tried Batteries or Core enough yet,
we have constraints, and we must make sure that if we rely on the some
library, the library fit these constraints. For example, I know that
Core has not been tested on Windows, and I don't know for Batteries.
Also, we want to separate between "lang" and "system", i.e. modules that
can be implemented with the core language, and modules that have system
dependencies.

Finally, unlike other companies using OCaml, we want to provide support
on the language itself, which means the compilers, other dev tools, and
also basic libraries. So, at some point, we will have to contribute to
either Core or Batteries, or both, but before that, we need to think
more about our own idea of what a good standard library should be, to
choose the best candidate from our point of view.

Fabrice

[-- Attachment #2: fabrice_le_fessant.vcf --]
[-- Type: text/x-vcard, Size: 380 bytes --]

begin:vcard
fn:Fabrice LE FESSANT
n:LE FESSANT;Fabrice
org:INRIA Saclay -- Ile-de-France;P2P & OCaml
adr;quoted-printable:;;Parc Orsay Universit=C3=A9 ;Orsay CEDEX;;91893;France
email;internet:fabrice.le_fessant@inria.fr
title;quoted-printable:Charg=C3=A9 de Recherche
tel;work:+33 1 74 85 42 14
tel;fax:+33 1 74 85 42 49 
url:http://fabrice.lefessant.net/
version:2.1
end:vcard


  parent reply	other threads:[~2011-11-04  9:55 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-11-02 18:29 forum
2011-11-03  8:08 ` David MENTRE
2011-11-03 18:14   ` forum
2011-11-03 20:15     ` Fabrice Le Fessant
2011-11-04  9:24       ` rixed
2011-11-04  9:34         ` Anil Madhavapeddy
2011-11-04  9:47         ` Thomas Gazagnaire
2011-11-04 11:25           ` Daniel Bünzli
2011-11-04 12:45             ` forum
2011-11-04 13:03               ` Daniel Bünzli
2011-11-04 17:08             ` Romain Bardou
2011-11-04 18:05               ` Daniel Bünzli
2011-11-04 18:12                 ` Thomas Gazagnaire
2011-11-04  9:55         ` Fabrice Le Fessant [this message]
2011-11-04 13:26           ` Edgar Friendly
2011-11-04 10:18 ` Gerd Stolpmann
2011-11-04 12:30   ` forum

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=4EB3B6A9.7090506@inria.fr \
    --to=fabrice.le_fessant@inria.fr \
    --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).