caml-list - the Caml user's mailing list
 help / color / mirror / Atom feed
From: james woodyatt <jhw@wetware.com>
To: Oleg <oleg_inconnu@myrealbox.com>
Cc: caml-list@inria.fr
Subject: Re: [Caml-list] Doubly-linked list
Date: Mon, 19 Aug 2002 16:17:16 -0700	[thread overview]
Message-ID: <CD4A176C-B3C9-11D6-86D7-000502DB38F5@wetware.com> (raw)
In-Reply-To: <200208130759.DAA26086@dewberry.cc.columbia.edu>

On Tuesday, Aug 13, 2002, at 01:00 US/Pacific, Oleg wrote:
>
> Has anyone implemented a doubly-linked list with O(1) push_back, 
> push_front,
> back, front, length operations?
>
> Thanks
> Oleg
>
> 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 have recently been working on a fully-persistent, catenable deque 
that uses explicit recursive slowdown , á la Kaplan and Tarjan, to 
achieve what seems to me to be O(1) amortized cost for all the 
traditional operations.  I think my design may be substantially simpler 
than algorithms I've seen published to date, but I'm not sure.  I'm 
certain it isn't O(1) for all operations, but I can push and shift 
millions of objects into and out of a deque without any noticeable 
degradation in performance over the size of a deque.  In other words, 
it looks to me to be good enough for government work.

When I've put the code through some more paces, I will publish it.  
Give me a few more weeks.


--james

-------------------
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-19 23:17 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
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 ` james woodyatt [this message]

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=CD4A176C-B3C9-11D6-86D7-000502DB38F5@wetware.com \
    --to=jhw@wetware.com \
    --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).