From: Keith Wansbrough <Keith.Wansbrough@cl.cam.ac.uk>
To: Alex Baretta <alex@baretta.com>
Cc: David Brown <caml-list@davidb.org>, caml-list@pauillac.inria.fr
Subject: Re: [Caml-list] Recursive lists
Date: Sat, 09 Oct 2004 09:32:13 +0100 [thread overview]
Message-ID: <E1CGCeH-0006F1-00@mta1.cl.cam.ac.uk> (raw)
In-Reply-To: Your message of "Fri, 08 Oct 2004 19:19:58 +0200." <4166CC3E.3080909@baretta.com>
Alex Baretta wrote:
> David Brown wrote:
> > On Fri, Oct 08, 2004 at 04:42:44PM +0200, Alex Baretta wrote:
> >
> >>Keith Wansbrough wrote:
> >
> > I doubt that most users of list operations want the extra overhead needed
> > to check for cycles. Recursive lists are fairly rare in strict languages.
Please be careful with your attributions. I did not write this
comment; David Brown did. I do entirely agree, though. And I
reiterate my earlier point - if you have an algorithm that uses a
potentially-cyclic datastructure and depends on detecting cycles, you
should build in some cycle-detection into the datastructure. You
should not depend on fragile and underspecified operations like
pointer equality.
Alex, I didn't understand your earlier point about needing to compare
*tails* of visited nodes - why is just comparing nodes not sufficient?
Surely if two nodes compare physically equal, their tails must also be
equal.
--KW 8-)
-------------------
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:[~2004-10-09 8:32 UTC|newest]
Thread overview: 45+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-08 13:20 Luca Pascali
2004-10-08 13:31 ` Keith Wansbrough
2004-10-08 14:32 ` skaller
2004-10-08 14:42 ` Alex Baretta
2004-10-08 15:43 ` David Brown
2004-10-08 17:19 ` Alex Baretta
2004-10-08 23:29 ` skaller
2004-10-09 8:35 ` Keith Wansbrough
2004-10-09 9:07 ` skaller
2004-10-09 8:32 ` Keith Wansbrough [this message]
2004-10-08 17:18 ` Wolfgang Lux
2004-10-11 0:44 ` Brian Hurt
2004-10-11 6:32 ` William Lovas
2004-10-11 6:52 ` Ville-Pertti Keinonen
2004-10-13 11:29 ` Alex Baretta
2004-10-13 11:22 ` Alex Baretta
2004-10-11 9:04 ` Keith Wansbrough
2004-10-08 14:05 ` Sébastien Furic
2004-10-08 14:44 ` Alex Baretta
2004-10-08 15:09 ` Jon Harrop
2004-10-08 15:13 ` james woodyatt
2004-10-08 14:26 ` sejourne_kevin
2004-10-08 18:28 ` Alex Baretta
2004-10-11 8:01 ` Jean-Christophe Filliatre
2004-10-11 9:20 ` Diego Olivier Fernandez Pons
2004-10-11 13:38 ` [Caml-list] About Obj (was Recursive lists) Christophe Raffalli
2004-10-11 13:49 ` [Caml-list] " Christophe Raffalli
2004-10-11 15:33 ` [Caml-list] " Jon Harrop
2004-10-11 16:09 ` Richard Jones
2004-10-11 16:40 ` [Caml-list] About Obj Yamagata Yoriyuki
2004-10-13 11:59 ` Alex Baretta
2004-10-11 16:24 ` [Caml-list] About Obj (was Recursive lists) james woodyatt
2004-10-11 16:46 ` brogoff
2004-10-11 17:24 ` james woodyatt
2004-10-12 0:19 ` skaller
2004-10-20 22:10 ` Greg K
2004-10-12 15:19 ` Christophe Raffalli
2004-10-13 11:42 ` Alex Baretta
2004-10-13 21:19 ` brogoff
2004-10-14 9:52 ` Andreas Rossberg
2004-10-14 17:38 ` brogoff
2004-10-15 8:22 ` Alex Baretta
2004-10-15 17:02 ` brogoff
2004-10-17 13:42 ` Alex Baretta
2004-10-12 6:17 ` [Caml-list] Recursive lists sejourne_kevin
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=E1CGCeH-0006F1-00@mta1.cl.cam.ac.uk \
--to=keith.wansbrough@cl.cam.ac.uk \
--cc=alex@baretta.com \
--cc=caml-list@davidb.org \
--cc=caml-list@pauillac.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