caml-list - the Caml user's mailing list
 help / color / mirror / Atom feed
From: Nicolas George <nicolas.george@ens.fr>
To: caml-list@inria.fr
Subject: Re: [Caml-list] OCaml standard library improvement
Date: Fri, 21 Feb 2003 18:23:13 +0100	[thread overview]
Message-ID: <20030221172313.GA7908@clipper.ens.fr> (raw)
In-Reply-To: <Pine.LNX.4.33.0302211046340.2037-100000@eagle.ancor.com>

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

Le tridi 3 ventôse, an CCXI, Brian Hurt a écrit :
> - We shouldn't be afraid to add functions/functionality to libraries.  
> There should never be a string2 library, let alone a string17 library.
[...]
> So the string library would be a collection of simple routines.  None of
> the routines in string call each other, or any common 'infrastructure'
> routines.

I think you misunderstoud the problem I was mentionning. A string
library should be one module, we agree. Let's say it is "String". Then
as soon as you use one function of the String module, the resulting
binary will hold _all_ the code in the String module. If you have a lot
of functions in the module (and this is what we want), you have a huge
binary. Berk.

As far as I know, there is no hack to avoid it. It would be necessary to
rethink the format of the .cmo or .cma files to allow that.

[-- Attachment #2: Type: application/pgp-signature, Size: 185 bytes --]

  reply	other threads:[~2003-02-21 17:23 UTC|newest]

Thread overview: 36+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-02-18 18:03 [Caml-list] Hashtbl.keys Oliver Bandel
2003-02-18 18:13 ` Hal Daume III
2003-02-20  9:43 ` Xavier Leroy
2003-02-20 16:54   ` [Caml-list] OCaml standard library improvement Stefano Zacchiroli
2003-02-21 13:47     ` Nicolas George
2003-02-22 14:09       ` Stefano Zacchiroli
2003-02-23 18:33         ` Alessandro Baretta
2003-02-21 13:53     ` fva
2003-02-21 16:18       ` Amit Dubey
2003-02-21 17:10         ` Brian Hurt
2003-02-21 17:23           ` Nicolas George [this message]
2003-02-21 18:01             ` Brian Hurt
2003-02-21 18:57               ` Chris Hecker
2003-02-21 19:28                 ` Brian Hurt
2003-02-22 15:52             ` John Max Skaller
2003-02-21 17:32         ` Maxence Guesdon
2003-02-24  1:21       ` Nicolas Cannasse
2003-02-24  1:45         ` Chris Hecker
2003-02-24  2:46           ` Brian Hurt
2003-02-24  7:42             ` Stefano Zacchiroli
2003-02-24 10:18             ` fva
2003-02-24 11:03             ` Amit Dubey
2003-02-24 12:56               ` John Max Skaller
2003-02-24 13:06                 ` Lauri Alanko
2003-02-24 13:08                 ` Sven Luther
2003-02-24 14:05                   ` [Caml-list] Library Discussion Followups Amit Dubey
2003-02-25  5:49                   ` [Caml-list] OCaml standard library improvement John Max Skaller
2003-02-25  8:29                     ` Xavier Leroy
2003-02-24 16:50                 ` Benjamin C. Pierce
2003-02-24 17:28                   ` brogoff
2003-02-25 18:08                   ` Diego Olivier Fernandez Pons
2003-02-26  7:47                     ` Jean-Christophe Filliatre
2003-02-25 10:47     ` [Caml-list] OCaml standard library _improvement_ NOT a new library! Stefano Zacchiroli
2003-02-25 21:43       ` Alessandro Baretta
2003-02-26  9:42         ` Stefano Zacchiroli
2003-02-21  6:40   ` [Caml-list] Hashtbl.keys Alex Cowie

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=20030221172313.GA7908@clipper.ens.fr \
    --to=nicolas.george@ens.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).