tao (Mr. Tao)
- Login: tao
- Registered on: 10/06/2016
- Last sign in: 07/16/2017
Issues
| open | closed | Total | |
|---|---|---|---|
| Assigned issues | 0 | 0 | 0 |
| Reported issues | 0 | 1 | 1 |
Activity
10/15/2016
-
04:29 PM Ruby Bug #12814: Pathname#each_child(false) produces unusable file paths
- I see… Still I can't decide whether it is for good or not. What is the purpose of such a path then? Shouldn't a String object instead of a Pathname be returned in such a case?
In my scenario I traverse directories and process some of ...
10/06/2016
-
- Sorry, I over edited my post. Argument to pathname is some existing folder, even `'..'` produces the error.
~~~ ruby
>> Pathname.new('..').each_child(false) { |f| p f.realpath }
~~~
~~~none
Errno::ENOENT: No such file or directory... -
- I tried to iterate over items in a directory with `each_child` testing each item whether it is a directory or not with `directory?`. This was working just fine until I added **`false`** as an argument to `each_child`.
~~~ ruby
Pathna...