[ruby-core:77501] [Ruby trunk Bug#12814] Pathname#each_child(false) produces unusable file paths

From: tao@...
Date: 2016-10-06 11:38:54 UTC
List: ruby-core #77501
Issue #12814 has been reported by Mr. Tao.

----------------------------------------
Bug #12814: Pathname#each_child(false) produces unusable file paths
https://bugs.ruby-lang.org/issues/12814

* Author: Mr. Tao
* Status: Open
* Priority: Normal
* Assignee: 
* ruby -v: ruby 2.3.1p112 (2016-04-26 revision 54768) [x86_64-darwin15]
* Backport: 2.1: UNKNOWN, 2.2: UNKNOWN, 2.3: UNKNOWN
----------------------------------------
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
Pathname.new('.').each_child { |f| p f.realpath } # works as expected
Pathname.new('.').each_child(false) { |f| p f.realpath } # throws an error
~~~

As per Ruby doc `By default, the yielded pathnames will have enough information to access the files.`, however pathnames yielded with `with_directory=false` are completely useless as file paths.



-- 
https://bugs.ruby-lang.org/

Unsubscribe: <mailto:ruby-core-request@ruby-lang.org?subject=unsubscribe>
<http://lists.ruby-lang.org/cgi-bin/mailman/options/ruby-core>

In This Thread

Prev Next