caml-list - the Caml user's mailing list
 help / color / mirror / Atom feed
From: "Anton E. Moscal" <msk@mail.tepkom.ru>
To: Oleg <oleg_inconnu@myrealbox.com>, "Anton Moscal" <msk@mail.tepkom.ru>
Cc: <caml-list@inria.fr>
Subject: Re: [Caml-list] Doubly-linked list
Date: Tue, 13 Aug 2002 22:23:20 +0400	[thread overview]
Message-ID: <20020813182248Z4350324-9727+7354@gnome04.net.rol.ru> (raw)
In-Reply-To: <200208131611.MAA00208@dewberry.cc.columbia.edu>

13 Aug 2002 20:12, Oleg wrote:

> >  O> be purely functional? It's hard for me to think of an efficient
> >  O> purely  functional doubly-linked list.
> >
> > For example:
> >
> > type 'a dll = 'a list (* before *) * 'a * 'a list (* next *)
>
> I don't think this is a doubly-linked list.  In a doubly-linked listl,
> _each_ element contains "references" to the next and previous elements. In
> your dll type, there is only one such element.
>
> Anyways, in O'Reilly book (and a verion posted to the list about two years
> ago), there is something similar to
>
> type 'a dlist = {mutable prev : 'a dlist option;
>                      mutable next : 'a dlist option;
>                      info : 'a}

This isn't "purely functional" :)
>
> But I don't think it's very practically usable in its vanilla form. I
> wouldn't use a doubly-linked list implementation unles it provided
> O(1) push_back, push_front, back, front, length (?), insert_before,
> insert_after, erase.

insert_before, erase (AKA empty), length in my representation are 
straightforward. push_back, push_front etc are more complex, but probably - 
asymtotically O(1). 

Really, my solution is a variarion on theme of the purely functional queue 
which can be found in Okasaki (or surprisingly - in the Gries "Science of 
programming" :) )

Anton
-------------------
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


  parent reply	other threads:[~2002-08-15  9:19 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 [this message]
2002-08-13 16:16   ` Brian Rogoff
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=20020813182248Z4350324-9727+7354@gnome04.net.rol.ru \
    --to=msk@mail.tepkom.ru \
    --cc=caml-list@inria.fr \
    --cc=oleg_inconnu@myrealbox.com \
    /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).