Bug #11638: [doc] misleading IO.write offset description

• Status: Closed
• Assignee: -
• Target version: -
• Backport: 2.2: DONTNEED, 2.3: DONE, 2.4: DONE

[akostadinov (Aleksandar Kostadinov)]

"If offset is not given, the file is truncated. Otherwise, it is not truncated."

The above is NOT true when 'a' mode is used. I'd suggest to clarify in documentation that offset is usually 0 if not specified but in 'a' mode it is at end of file or something along these lines.

http://ruby-doc.org/core-2.2.0/IO.html#method-c-write

[takanabe (Takayuki Watanabe)]

Yes. When we use appending mode without offset, the file is not truncated.
Truncating files are occurred in write mode only. So it seems that we should just add the behaviour in write mode rather than adding behaviour in append mode.

I created PR for this ticket on github: https://github.com/ruby/ruby/pull/1571

[hsbt (Hiroshi SHIBATA)]

• Status changed from Open to Closed

Applied in changeset trunk|r60294.

---

Clarify the behavior of IO.write without offset in write mode.

https://github.com/ruby/ruby/pull/1571

Patch by @takanabe [fix GH-1571]
[Bug #11638][ruby-core:71277]

[hsbt (Hiroshi SHIBATA)]

• Backport changed from 2.0.0: UNKNOWN, 2.1: UNKNOWN, 2.2: UNKNOWN to 2.2: DONTNEED, 2.3: REQUIRED, 2.4: REQUIRED

[nagachika (Tomoyuki Chikanaga)]

• Backport changed from 2.2: DONTNEED, 2.3: REQUIRED, 2.4: REQUIRED to 2.2: DONTNEED, 2.3: REQUIRED, 2.4: DONE

ruby_2_4 r62692 merged revision(s) 60294.

[usa (Usaku NAKAMURA)]

• Backport changed from 2.2: DONTNEED, 2.3: REQUIRED, 2.4: DONE to 2.2: DONTNEED, 2.3: DONE, 2.4: DONE

ruby_2_3 r62823 merged revision(s) 60294.