From: Sylvain Le Gall <sylvain@le-gall.net>
To: caml-list@inria.fr
Subject: [Caml-list] Re: howto: recursively iterate over filesystem
Date: Tue, 3 Jul 2012 19:50:49 +0000 (UTC) [thread overview]
Message-ID: <slrnjv6j8p.drt.sylvain@gallu.homelinux.org> (raw)
In-Reply-To: <481061341303698@web18d.yandex.ru>
On 03-07-2012, Ivan <ivg@ieee.org> wrote:
> Merсi, it looks nice! But I didn't understand what's the issue with links. The FilePath.mli file contains a
> warning, that I've failed to understand:
> 32 This module manipulate abstract path that are not bound to a real filesystem.
> 33 In particular, it makes the assumption that there is no symbolic link that
> 34 should modify the meaning of a path. If you intend to use this module
> 35 against a real set of filename, the best solution is to apply to every
> 36 filename to solve symbolic link through {!FileUtil.readlink}.
>
> In my situation a folder, which I'd like to traverse, is plenty of links.
> Maybe someone can clarify it for me?
>
Links modify the meaning of paths and it is not clear how to react to
this.
E.g,
/a/b/c is a link to /a/b/d/e. How do you interpet /a/b/c/.. ?
Will it reduce to /a/b or to /a/b/d ?
The answer to this question is "open" to interpretation...
BTW, FileUtil.find is protected against recursive links and so on...
Cheers,
Sylvain Le Gall
--
Linkedin: http://fr.linkedin.com/in/sylvainlegall
Start an OCaml project here: http://forge.ocamlcore.org
OCaml blogs: http://planet.ocamlcore.org
next prev parent reply other threads:[~2012-07-03 19:51 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-03 3:30 [Caml-list] " Ivan
2012-07-03 3:42 ` Rudi Grinberg
2012-07-03 6:19 ` Stéphane Glondu
2012-07-03 8:21 ` Ivan
2012-07-03 8:24 ` Gabriel Scherer
2012-07-03 8:33 ` Ivan
2012-07-03 8:45 ` Adrien
2012-07-03 8:46 ` Fabrice Le Fessant
2012-07-03 9:25 ` Ivan
2012-07-03 12:04 ` Eric Cooper
2012-07-03 12:28 ` Daniel Bünzli
2012-07-03 19:50 ` Sylvain Le Gall [this message]
2012-07-03 12:14 ` Daniel Bünzli
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=slrnjv6j8p.drt.sylvain@gallu.homelinux.org \
--to=sylvain@le-gall.net \
--cc=caml-list@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