So what would that look like?  Is it sufficient to throw every
canonical directory path in a set and test for membership before
traversing down any directory?  Or is that even sufficient because you
could arrive at the same location through different paths...  I wonder
if you can get something more unique, like an inode ID or something
along those lines?

On Feb 1, 11:21 pm, ataggart <alex.tagg...@gmail.com> wrote:
> On Feb 1, 2:14 pm, Jim Van Donsel <j...@jimandbarb.net> wrote:
>
> > Fair enough.
>
> > But I guess the moral is that a file-seq should not be used unless you
> > have a well-controlled filesystem.
>
> Or more generally, all sequences may be infinite unless you know the
> backing data has no cycles, or you have some terminating/filtering
> conditions.

-- 
You received this message because you are subscribed to the Google
Groups "Clojure" group.
To post to this group, send email to clojure@googlegroups.com
Note that posts from new members are moderated - please be patient with your 
first post.
To unsubscribe from this group, send email to
clojure+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/clojure?hl=en

Reply via email to