Bug #5782
closedFile.binwrite doc and hash argument
Description
The doc for File.binwrite
doesn't mention the possibility of a fourth argument (option hash), unlike File.write
. Judging from the code, this looks like an oversight.
Can we get confirmation that it does accept a fourth parameter and that the doc should be updated?
I would personally simplify the rdoc to state that it File.binwrite
does exactly the same as File.write
except that it opens the file in binary mode.
Noticed by Konstantin Haase.
Thanks,¶
Marc-Andre
Updated by marcandre (Marc-Andre Lafortune) about 12 years ago
For some reason, this bug report was never posted on the mailing list:
The doc for File.binwrite
doesn't mention the possibility of a fourth argument (option hash), unlike File.write
. Judging from the code, this looks like an oversight.
Can we get confirmation that it does accept a fourth parameter and that the doc should be updated?
I would personally simplify the rdoc to state that it File.binwrite
does exactly the same as File.write
except that it opens the file in binary mode.
Noticed by Konstantin Haase.
Thanks,¶
Marc-Andre
Updated by naruse (Yui NARUSE) about 12 years ago
- Status changed from Open to Assigned
- Assignee set to sorah (Sorah Fukumori)
Updated by sorah (Sorah Fukumori) about 12 years ago
- Status changed from Assigned to Closed
- % Done changed from 0 to 100
This issue was solved with changeset r34967.
Marc-Andre, thank you for reporting this issue.
Your contribution to Ruby is greatly appreciated.
May Ruby be with you.
- io.c: fix rdoc of
IO.binwrite
to show same asIO.write
except
it opens file with mode "wb:ASCII-8BIT". [Bug #5782] [ruby-core:42592]