Project

General

Profile

Actions

Bug #5568

closed

IO#set_encoding ignores internal when the same as external only when specified as "ext:int"

Added by brixen (Brian Shirai) over 12 years ago. Updated about 12 years ago.

Status:
Closed
Target version:
-
ruby -v:
ruby 2.0.0dev (2011-10-26 trunk 33526) [x86_64-darwin10.8.0]
Backport:
[ruby-core:40727]

Description

When passing two encoding objects that are the same to IO#set_encoding, both external and internal encodings for the IO instance are set.

However, when passing "ext:int", the internal encoding is not set if the same as external, but a warning is issued. Further, when passing "ext", "int", the internal encoding is not set and no warning is issued.

sasha:rubinius brian$ ruby2.0 -v -e 'p STDOUT.set_encoding("utf-8:utf-8").internal_encoding'
ruby 2.0.0dev (2011-10-26 trunk 33526) [x86_64-darwin10.8.0]
-e:1: warning: Ignoring internal encoding utf-8: it is identical to external encoding utf-8
nil

sasha:rubinius brian$ ruby2.0 -v -e 'p STDOUT.set_encoding(Encoding::UTF_8, Encoding::UTF_8).internal_encoding'
ruby 2.0.0dev (2011-10-26 trunk 33526) [x86_64-darwin10.8.0]
#Encoding:UTF-8

sasha:rubinius brian$ ruby2.0 -v -e 'p STDOUT.set_encoding("utf-8", "utf-8").internal_encoding'
ruby 2.0.0dev (2011-10-26 trunk 33526) [x86_64-darwin10.8.0]
nil

Is there a reason for these differences?

Thanks,
Brian


Related issues 1 (0 open1 closed)

Related to Ruby master - Bug #6324: Spurious/incorrect warning on File.open with internal_encoding specified in string mode to duplicate external_encodingClosednaruse (Yui NARUSE)04/20/2012Actions
Actions

Also available in: Atom PDF

Like0
Like0Like0Like0Like0Like0