Bug #6947
closedDocumentation for Pathname
Description
I've added a documentation patch for Pathname.
Files
Updated by drbrain (Eric Hodel) about 12 years ago
I think there is too much "actually", just "It doesn't access the filesystem" is sufficient.
For freeze, taint and untaint I think "Freezes this Pathname", "Taints this Pathname", "Untaints this Pathname" is a better description.
I think all the "This method has been available since" can be removed since they all predate 1.8.7.
I think the first sentence of the Pathname class comment could be improved. How about "A Pathname represents the name of a file on the filesystem, but not the file itself."
Updated by zzak (zzak _) about 12 years ago
Hi Eric!
Thanks for feedback, much appreciated.
I'll upload a patch with your changes, probably this evening.
One thing I might change is the Pathname intro, since a Pathname can represent a file or a directory:
"Pathname represents the name of a file or directory on the filesystem, but not the file itself."
Not sure if you meant "A Pathname represents ..", I kinda like just "Pathname represents .." better.
Updated by drbrain (Eric Hodel) about 12 years ago
"Pathname represents ..." is good
Updated by zzak (zzak _) about 12 years ago
Hi Eric!
Here's the patch we discussed, see 0002-*-Pathname.patch
Thanks
Updated by drbrain (Eric Hodel) about 12 years ago
This looks good, please commit it.
Updated by drbrain (Eric Hodel) about 12 years ago
- Assignee changed from drbrain (Eric Hodel) to zzak (zzak _)
Updated by zzak (zzak _) about 12 years ago
- Status changed from Open to Closed
- % Done changed from 0 to 100
This issue was solved with changeset r36950.
Zachary, thank you for reporting this issue.
Your contribution to Ruby is greatly appreciated.
May Ruby be with you.
- ext/pathname/lib/pathname.rb: Documentation for Pathname.
- ext/pathname/pathname.c: ditto.
[Bug #6947] [ruby-core:47354]