On Tuesday, Sep 9, 2003, at 21:33 Australia/Brisbane, Robert Brenstein <[EMAIL PROTECTED]> wrote:
snip
Hmm, actually, when one walks directories, shouldn't one walk only the true directories and treat aliases as files (which they are)?
Yes. As I intimated in my previous post, and have now verified again by experiment, the walker is *not* fooled by an alias.
I created this structure on a separate volume called "sliver":
tmp
a real file, called "CRS BC Report.mell"
a real directory, called "parent of fake"
an alias to "tmp"
On being asked to walk this, the handler returned two files as follows: /Volumes/sliver/tmp/CRS+BC+Report.mell /Volumes/sliver/tmp/parent of fake/tmp with maxDepth of 2, and did not loop. This is correct behaviour.
The problem I described in my previous post does not arise from an alias, but from a reference in //Networks to "[your computer name].local." which kicks off the cycling.
regards David
Robert
_______________________________________________ use-revolution mailing list [EMAIL PROTECTED] http://lists.runrev.com/mailman/listinfo/use-revolution
