Project

General

Profile

Actions

Bug #5859

closed

incorrect return value of Pathname.realdirpath of Pathname objects created by Pathname.entries

Added by tommylommykins (Thomas Green) over 12 years ago. Updated over 12 years ago.

Status:
Closed
Assignee:
-
Target version:
ruby -v:
ruby 1.9.3p0 (2011-10-30 revision 33570) [x86_64-linux]
Backport:
[ruby-core:41959]

Description

It appears when calling realdirpath on a Pathname object returned by Pathname#entries, the returned value is always the current working directory of the ruby process, instead of the location of the file in the filesystem
This disagrees with the rdoc description of Pathname#realdirpath, which does state that realdirpath will return the absolute name of the file.

Tho following code demonstrates the issue:

mkdir /tmp/thing
touch /tmp/thing/a
cd ~
ruby-1.9.3-p0 -ve "require 'pathname'; puts Pathname.new('/tmp/thing').entries.sort[2].realdirpath"

This is the output from the ruby process:

ruby 1.9.3p0 (2011-10-30 revision 33570) [x86_64-linux]
/home/t/a

According to my interpretation of the description in rdoc, the correct output should be "/tmp/thing/a"
http://www.ruby-doc.org/stdlib-1.9.3/libdoc/pathname/rdoc/Pathname.html#method-i-realdirpath

Actions

Also available in: Atom PDF

Like0
Like0Like0Like0Like0Like0