Re: Pathname#walk for traversing path nodes (patch)

Evan Webb wrote:
> I'd prefer each_sub, each_subdir, or something to that effect. Makes
> the method much clearer regards it's operation.

Coming up with a name for this method is a bit of a problem. #each_dir,
in fact, was my first choice but it (as well as #each_sub and such)
could imply that it would treat _all_ subdirectories in each node of
the path, which is not true.

The absolute best name would be simply #each (incidentally, looks like
it would be available). That failing, #walk, #traverse or #each_node.

 >> Pathname.new('/etc/init.d/foo').each {|node| p node.realpath}
"/"
"/etc/"
"/etc/init.d/"
"/etc/init.d/foo"
=> "/etc/init.d/foo"

> - Evan
> 
> On 8/22/05, David A. Black <[e-mail]> wrote:
> 
>>Hi --
>>
>>On Mon, 22 Aug 2005, Tanaka Akira wrote:
>>
>>
>>>In article <[e-mail]>,
>>> ES <[e-mail]> writes:
>>>
>>>
>>>>Here is a small addition to Pathname against 1.9, probably suited
>>>>for 1.8. Makes doing something for each node in a path easier.
>>>
>>>I'm not sure that "walk" is a good name.
>>>
>>>At first look, I expected "walk" is an alias to "find" which traverse
>>>all files under the pathname.
>>>(I know os.path.walk in Python.)
>>
>>Maybe "scan".
>>
>>
>>David
>>
>>--
>>David A. Black
>>[e-mail]
>>

E

-- 
template<typename duck>
void quack(duck& d) { d.quack(); }