From: "Nicolas Cannasse" <warplayer@free.fr>
To: <skaller@users.sourceforge.net>, "Richard Jones" <rich@annexia.org>
Cc: "caml-list" <caml-list@inria.fr>
Subject: Re: [Caml-list] Should be INSIDE STANDARD-LIB: Hashtbl.keys
Date: Sat, 24 Apr 2004 11:20:23 +0200 [thread overview]
Message-ID: <005501c429dd$5f478390$19b0e152@warp> (raw)
In-Reply-To: <1082771932.21205.654.camel@pelican.wigram>
> On Sat, 2004-04-24 at 01:03, Richard Jones wrote:
> > Maybe there's no good behaviour, but I keep writing a 'keys' function
> > in almost every program I've written which uses Hashtbl, which
> > certainly suggests that something is missing.
>
> The problem is that the Ocaml hashtbl isn't a conventional
> hash table. It allows multiple bindings which means it
> cannot be treated as a simple container.
>
> I spend some time making sure I don't use that
> feature by mistake.
>
> Similar 'too rich' functionality exists for
> many data types, for example mutable strings and arrays.
> On the other hand some functionality is missing,
> for example variable length arrays.
>
> The former can be fixed easily by the client
> building a wrapper library with restricted functionality.
>
> The latter *needs* to be added to the standard
> library urgently because it cannot be implemented
> at all in Ocaml without magic, and it is a very
> useful and important data structure to have.
You can have a look at the nice DynArray module from the ExtLib :
http://ocaml-lib.sf.net
Regards,
Nicolas Cannasse
-------------------
To unsubscribe, mail caml-list-request@inria.fr Archives: http://caml.inria.fr
Bug reports: http://caml.inria.fr/bin/caml-bugs FAQ: http://caml.inria.fr/FAQ/
Beginner's list: http://groups.yahoo.com/group/ocaml_beginners
next prev parent reply other threads:[~2004-04-24 9:22 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-04-21 1:19 Oliver Bandel
2004-04-21 8:39 ` Richard Jones
2004-04-21 9:13 ` Martin Jambon
2004-04-23 12:51 ` Xavier Leroy
2004-04-23 13:05 ` Jean-Baptiste Rouquier
2004-04-23 16:04 ` Xavier Leroy
2004-04-23 18:21 ` Jon Harrop
2004-04-23 21:31 ` Jon Harrop
2004-04-23 21:53 ` John Goerzen
2004-04-26 6:28 ` Florian Hars
2004-04-23 18:29 ` John Goerzen
[not found] ` <20040423190710.GA1506@first.in-berlin.de>
2004-04-23 20:42 ` John Goerzen
2004-04-23 15:03 ` Richard Jones
2004-04-24 1:58 ` skaller
2004-04-24 9:20 ` Nicolas Cannasse [this message]
2004-04-24 19:26 ` skaller
2004-04-26 7:29 ` Jean-Christophe Filliatre
2004-04-23 16:06 ` Brian Hurt
2004-04-23 16:31 ` Martin Jambon
2004-04-23 17:27 ` Christoph Bauer
2004-04-23 18:29 ` John Goerzen
[not found] ` <20040423191010.GB1506@first.in-berlin.de>
2004-04-23 20:41 ` John Goerzen
[not found] ` <20040424080904.GA821@first.in-berlin.de>
2004-04-24 20:59 ` John Goerzen
2004-04-25 8:12 ` Oliver Bandel
2004-04-23 18:28 ` John Goerzen
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='005501c429dd$5f478390$19b0e152@warp' \
--to=warplayer@free.fr \
--cc=caml-list@inria.fr \
--cc=rich@annexia.org \
--cc=skaller@users.sourceforge.net \
/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