From: kcheung@math.carleton.ca
To: caml-list@yquem.inria.fr
Subject: Re: [Caml-list] ocamlgraph predecessors
Date: Mon, 10 Aug 2009 08:19:35 -0400 (EDT) [thread overview]
Message-ID: <60096.70.26.45.246.1249906775.squirrel@pegasus.carleton.ca> (raw)
In-Reply-To: <20090810.105950.42868244.garrigue@math.nagoya-u.ac.jp>
Perhaps something like that in ConcreteBidirectional
be implemented for general Digraph so predecessors
can be accessed in O(1)? If I am not mistaken, that
will double the storage and running time of most of
the operations. This implementation could be added
as an additional variant without modifying existing
code.
Kevin Cheung.
> From: rixed@happyleptic.org
>> > What you're asking is similar to the problem of finding the
>> predecessor
>> > of an arbitrary node in a singly-linked-list. You have no option but
>> to
>> > scan the whole list to find its predecessor. If you had a
>> > doubly-linked-list, predecessor lookups would work easily, but that's
>> a
>> > different data structure, with much more overhead.
>>
>> Much more overhead, really ?
>> So this is for performance reasons that all functionnal languages
>> promote singly-linked lists, while for instance in Linux every list
>> is implemented with a doubly linked list for purely ideological reasons
>> ?
>>
>> :-)
>
> Yes indeed, much more overhead. But the source is not the fact you
> have to maintain backlinks, but their impact on the GC.
> With a GC, any modification on existing values has a cost, since you
> have to keep track of them independently of the value itself.
> Since linux has no GC, using doubly linked lists has only a very
> limited cost, mostly related to the extra space needed.
> By the way, BSD uses lots of singly-linked lists, probably because it
> comes from a time when there was not so much memory.
>
> Jacques Garrigue
>
> _______________________________________________
> Caml-list mailing list. Subscription management:
> http://yquem.inria.fr/cgi-bin/mailman/listinfo/caml-list
> Archives: http://caml.inria.fr
> Beginner's list: http://groups.yahoo.com/group/ocaml_beginners
> Bug reports: http://caml.inria.fr/bin/caml-bugs
>
next prev parent reply other threads:[~2009-08-10 12:19 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-09 18:32 rixed
2009-08-10 1:59 ` Jacques Garrigue
2009-08-10 12:19 ` kcheung [this message]
2009-08-10 17:46 ` Benjamin Ylvisaker
2009-08-12 22:40 ` Francis Dupont
-- strict thread matches above, loose matches on Subject: below --
2009-08-08 5:24 Benjamin Ylvisaker
2009-08-08 13:35 ` [Caml-list] " Edgar Friendly
2009-08-08 20:16 ` Benjamin Ylvisaker
2009-08-09 14:56 ` Edgar Friendly
2009-08-25 14:22 ` Julien Signoles
2009-08-25 14:22 ` Julien Signoles
2009-08-26 14:35 ` Benjamin Ylvisaker
2009-08-26 6:54 ` Jean-Christophe Filliâtre
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=60096.70.26.45.246.1249906775.squirrel@pegasus.carleton.ca \
--to=kcheung@math.carleton.ca \
--cc=caml-list@yquem.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