From: John Goerzen <jgoerzen@complete.org>
To: Jon Harrop <jdh30@cam.ac.uk>
Cc: caml-list@inria.fr
Subject: Re: [Caml-list] Should be INSIDE STANDARD-LIB: Hashtbl.keys
Date: Fri, 23 Apr 2004 16:53:33 -0500 [thread overview]
Message-ID: <20040423215333.GI6783@excelhustler.com> (raw)
In-Reply-To: <200404232231.36872.jdh30@cam.ac.uk>
On Fri, Apr 23, 2004 at 10:31:36PM +0100, Jon Harrop wrote:
> I should also say that I have never had any need for this function. What do
> you guys use it for?
One example is the sections function at
http://gopher.quux.org:70/devel/missinglib/html/ConfigParser.rawConfigParser.html.
Internally, a configuration file is represented as a hash of section
names to a hash of option names to values. (A hash of a hash of
strings, basically.) Sometimes, you might not know what sections to
expect up-front. Getting a list of the keys in the top-level hash will
return the needed information. This could occur for many reasons:
configuring multiple ISP accounts in a network tool, configuring
multiple database sources in an ODBC configuration, etc.
Here's a contrived example, but one I could imagine encountering: Having
a hash mapping filenames to data about them (say, from stat(2). Perhaps
you'd have a need sometimes to just get a list of files (maybe to copy
them elsewhere or display a list for the user).
Yes, one could use fold to do all of this. Point is, it's often easier
to just call "keys" and get a list. The raw performance may not always
matter. (Just witness the popularity of Ruby <g>)
-- John
-------------------
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-23 21:53 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 [this message]
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
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=20040423215333.GI6783@excelhustler.com \
--to=jgoerzen@complete.org \
--cc=caml-list@inria.fr \
--cc=jdh30@cam.ac.uk \
/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