From: Brian Rogoff <bpr@artisan.com>
To: Diego-Olivier.FERNANDEZ-PONS@cicrp.jussieu.fr
Cc: caml-list@inria.fr
Subject: Re: [Caml-list] Doubly-linked list
Date: Tue, 13 Aug 2002 09:16:41 -0700 [thread overview]
Message-ID: <15705.12521.60353.709909@granite.artisan.com> (raw)
In-Reply-To: <Pine.A32.3.95.1020813125617.63202A-100000@ibm1.cicrp.jussieu.fr>
Diego Olivier Fernandez Pons writes:
> Oleg a écrit :
>
> > P.S. BTW, one could have identical interfaces for a) resizable arrays, b)
> > doubly-linked lists and c) deques, the only difference being the efficiency
> > of various operations. It could be convenient for a programmer, because final
> > data representation can be chosen after the program has been profiled and
> > without changing much code. Has anyone tackled this problem?
>
> I will be soon releasing a data structure library (september) which
> includes a port of EDiSon (GHC/hslibs/data/Edison in the GHC CVS), all
> data structures that were in Okasaki's purely functional data
> structures book and some more (weight balanced trees, cartesian trees,
> priority search queues, ...)
I'm looking forward to seeing it. I get the impression that Edison uses
(multi-parameter) type classes so it isn't clear that it will translate
well. Oh yeah, I may as well add my biannual plea for some form of
overloading in OCaml, which is somewhere in the top 3 of my wishlist.
Anyways, doubly linked lists are a textbook example of an imperative data
structure, and, waddya know, a very good textbook (the Cousineau/Mauny one
which is owned by everyone on this list ;-) has this example pretty early
in the section on imperative programming. Look here for the source
http://pauillac.inria.fr/cousineau-mauny/main.html
but realize that you'll have to translate the source into OCaml. If I
remember correctly, the doubly linked list looks something like
type 'a t =
{ data : 'a;
mutable prev : 'a t;
mutable next : 'a t
}
let create e = let rec x = {data = e; prev = x; next = x} in x
etc.
which is very nice if you are used to trying such things in SML.
-- Brian
-------------------
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:[~2002-08-13 16:16 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-08-13 8:00 Oleg
2002-08-13 8:54 ` Markus Mottl
2002-08-13 15:52 ` Oleg
2002-08-13 11:00 ` Diego Olivier Fernandez Pons
2002-08-13 14:30 ` Oleg
2002-08-13 15:11 ` Anton Moscal
2002-08-13 16:12 ` Oleg
2002-08-13 17:16 ` Max Kirillov
2002-08-14 0:49 ` Max Kirillov
2002-08-13 18:23 ` Anton E. Moscal
2002-08-13 16:16 ` Brian Rogoff [this message]
2002-08-14 8:13 ` Diego Olivier Fernandez Pons
2002-08-14 15:43 ` Brian Rogoff
2002-08-19 10:38 ` Diego Olivier Fernandez Pons
2002-08-19 15:58 ` Polymorphic recursion 9Was Re: [Caml-list] Doubly-linked list) Brian Rogoff
2002-08-21 8:04 ` Diego Olivier Fernandez Pons
2002-08-21 15:48 ` Brian Rogoff
2002-08-23 8:14 ` Diego Olivier Fernandez Pons
2002-08-23 21:57 ` John Max Skaller
2002-08-27 13:00 ` Diego Olivier Fernandez Pons
2002-08-28 14:50 ` John Max Skaller
2002-08-28 17:27 ` [Caml-list] FELIX (was: Polymorphic recursion) Oleg
2002-08-19 23:17 ` [Caml-list] Doubly-linked list james woodyatt
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=15705.12521.60353.709909@granite.artisan.com \
--to=bpr@artisan.com \
--cc=Diego-Olivier.FERNANDEZ-PONS@cicrp.jussieu.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