From: sawadatsuyoshi@...
Date: 2020-03-25T05:50:08+00:00
Subject: [ruby-core:97593] [Ruby master Bug#16737] File::BINARY doesn't work

Issue #16737 has been updated by sawa (Tsuyoshi Sawada).


It's rather misleading to get `f.binmode? #=> true` and `f.external_encoding #=> #<Encoding:ASCII-8BIT>` with `'wb'`.

----------------------------------------
Bug #16737: File::BINARY doesn't work
https://bugs.ruby-lang.org/issues/16737#change-84776

* Author: sos4nt (Stefan Sch��ler)
* Status: Open
* Priority: Normal
* Backport: 2.5: UNKNOWN, 2.6: UNKNOWN, 2.7: UNKNOWN
----------------------------------------
`File.open` takes a `mode` argument which can be given as a string or as an integer using `File::Constants`.

When using the latter, the constant `File::BINARY` doesn't have any effect:

```ruby
# this works:
File.open('foo', 'wb') do |f|
  p f.binmode?
  p f.external_encoding
end
#=> true
#=> #<Encoding:ASCII-8BIT>


# this doesn't:
File.open('foo', File::WRONLY|File::TRUNC|File::CREAT|File::BINARY) do |f|
  p f.binmode?
  p f.external_encoding
end
#=> false
#=> nil
```

Further inspecting `File::BINARY` reveals that it has a value of zero:

```ruby
File::BINARY #=> 0
```

So it's no surprise that OR-ing it doesn't do anything.

I've tried various Ruby versions from 1.9.3 to 2.7.0 and all showed the above behavior. (I'm on macOS if that matters)

I'm aware that I can achieve the desired result by using a string mode or by passing `binary: true`. But since Ruby accepts `mode` to be given as an integer, there should be a (working) "b" equivalent.



-- 
https://bugs.ruby-lang.org/

Unsubscribe: <mailto:ruby-core-request@ruby-lang.org?subject=unsubscribe>
<http://lists.ruby-lang.org/cgi-bin/mailman/options/ruby-core>