So, it IS by design, then. I see.
Yes, I do need to recursively list files only. This is how I did it in my own
vocab:
: file-list ( path -- seq )
f recursive-directory-entries [ regular-file? ] filter ;
I realize this is cheating, because `regular-file?` (same as `directory?`
suggested below) is supposed to work on `file-info-tuple`, not on
`directory-entry`. It just so happens that they contain the same data under the
same slot name.
So, yes, I'd love to have that function officially supported.
23.07.2016, 23:29, "John Benediktsson" <mrj...@gmail.com>:
> Files are in the UNIX sense, which can be either files or directories. You
> can use `directory?` to exclude those if you need it.
>
> If that behavior is useful we could add a word that does it for you in the
> standard library.
>
>> On Jul 23, 2016, at 1:23 PM, Alexander Ilin <ajs...@yandex.ru> wrote:
>>
>> Hello!
>>
>> In the documentation for recursive-directory-files it says: "Traverses a
>> directory path recursively and returns a sequence of files in a
>> breadth-first or depth-first manner."
>>
>> I discovered that (on Windows) it actually returns a list that contains
>> both files AND directories.
>>
>> Is this by design? I found it confusing.
---=====---
Александр
------------------------------------------------------------------------------
What NetFlow Analyzer can do for you? Monitors network bandwidth and traffic
patterns at an interface-level. Reveals which users, apps, and protocols are
consuming the most bandwidth. Provides multi-vendor support for NetFlow,
J-Flow, sFlow and other flows. Make informed decisions using capacity planning
reports.http://sdm.link/zohodev2dev
_______________________________________________
Factor-talk mailing list
Factor-talk@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/factor-talk
