From: Francis Dupont <Francis.Dupont@fdupont.fr>
To: Jacques Garrigue <garrigue@math.nagoya-u.ac.jp>
Cc: rixed@happyleptic.org, caml-list@yquem.inria.fr
Subject: Re: [Caml-list] ocamlgraph predecessors
Date: Thu, 13 Aug 2009 00:40:26 +0200 [thread overview]
Message-ID: <200908122240.n7CMeQmX048236@givry.fdupont.fr> (raw)
In-Reply-To: Your message of Mon, 10 Aug 2009 10:59:50 +0900. <20090810.105950.42868244.garrigue@math.nagoya-u.ac.jp>
In your previous mail you wrote:
By the way, BSD uses lots of singly-linked lists, probably because it
comes from a time when there was not so much memory.
=> no, BSDs use an include ([/usr/include]/sys/queue.h) which provides
C macros for singly-linked lists, singly-linked tail queues, lists
and tail queues. So programmers just select the best data structure for
each job (and as BSD programmers are skilled programmers they use
signly-linked lists as soon as they don't need a list feature).
Note this is not very bound to memory: in many cases there are
some structures with better memory use, for instance lists in arrays
from Python (standard C implementation).
Thanks
Francis.Dupont@fdupont.fr
PS: just type "man queue" on a BSD (including MacOS X). If it is
not enough try "man tree" (but not yet on my MacOS X, sorry)...
next prev parent reply other threads:[~2009-08-12 22:40 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
2009-08-10 17:46 ` Benjamin Ylvisaker
2009-08-12 22:40 ` Francis Dupont [this message]
-- 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=200908122240.n7CMeQmX048236@givry.fdupont.fr \
--to=francis.dupont@fdupont.fr \
--cc=caml-list@yquem.inria.fr \
--cc=garrigue@math.nagoya-u.ac.jp \
--cc=rixed@happyleptic.org \
/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