caml-list - the Caml user's mailing list
 help / color / mirror / Atom feed
From: Brian Rogoff <bpr@best.com>
To: caml-list@inria.fr
Subject: [Caml-list] Petty complaints
Date: Tue, 24 Apr 2001 08:23:39 -0700 (PDT)	[thread overview]
Message-ID: <Pine.BSF.4.21.0104240810450.12262-100000@shell5.ba.best.com> (raw)

Hi,
    I'd like to be able to treat the types "defined" in the Pervasives
module as if they really were defined there. This way I could reuse 
type names like array, char, string, and list cleanly by referring to 
the built-ins by their qualified names. Why doesn't it work that way now?
It would even be nice to be able to have the OCaml library modules be 
referable by qualified names, like Pervasives.List, Pervasives.Array, etc...

    Someone recently got bit by the mutable nature of the OCaml built in 
strings. I looked at the mailing list and there was mention that a long 
time ago Caml had immutable strings (ropes?) and arrays, but that no one
used them. I'm building some stuff using version arrays now (Martin
Erwig's Functional Graph Library) and while they're simple enough to write
in OCaml I bet built in immutable arrays would be much faster.

-- Brian
 

-------------------
To unsubscribe, mail caml-list-request@inria.fr.  Archives: http://caml.inria.fr


             reply	other threads:[~2001-04-24 15:23 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-04-24 15:23 Brian Rogoff [this message]
2001-04-25  6:55 ` Fabrice Le Fessant
2001-04-25  7:00   ` Fabrice Le Fessant
  -- strict thread matches above, loose matches on Subject: below --
2001-04-02  4:26 [Caml-list] petty complaints Brian Rogoff
2001-04-02 13:32 ` Xavier Leroy
2001-04-02 15:24   ` Brian Rogoff
2001-04-02 20:17   ` Chris Hecker
2001-04-02 19:45     ` Brian Rogoff
2001-04-09  5:23 ` John Max Skaller
2001-04-09 15:34 ` Christian Lindig
2001-04-09 16:01   ` Brian Rogoff
2001-04-09 16:24   ` David McClain
2001-04-09 16:29   ` Pierre Weis
2001-04-10 22:25     ` Marcin 'Qrczak' Kowalczyk

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=Pine.BSF.4.21.0104240810450.12262-100000@shell5.ba.best.com \
    --to=bpr@best.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).