                                                                                                                                                                                                                                                                
Received-SPF: pass (google.com: domain of florgro+caf_=ruby-core-google-garchive-1974=googlegroups....@gmail.com designates 64.233.166.183 as permitted sender) client-ip=64.233.166.183;
Received-SPF: pass (google.com: domain of ruby-core-ad...@ruby-lang.org designates 221.186.184.68 as permitted sender) client-ip=221.186.184.68;
Date: Sun, 30 Sep 2007 13:44:55 +0900
Posted: Sun, 30 Sep 2007 00:44:28 -0400
From: Gary Wright <gwtm...@mac.com>
Reply-To: ruby-c...@ruby-lang.org
Subject: Re: String.force_encoding
To: ruby-c...@ruby-lang.org
Message-Id: <0984FDF3-CA20-4821-BC36-2D5FEB06D...@mac.com>
In-Reply-To: <6.0.0.20.2.20070929155000.0bb81510@localhost>
References: <46FDD70D.8040...@davidflanagan.com> <6.0.0.20.2.20070929155000.0bb81510@localhost>
Mime-Version: 1.0 (Apple Message framework v752.3)
Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed
Content-Transfer-Encoding: 7bit
Precedence: bulk
Lines: 27


On Sep 29, 2007, at 3:07 AM, Martin Duerst wrote:
> At 13:39 07/09/29, David Flanagan wrote:
>
>> I don't want to re-open a discussion if this decision has already  
>> been firmly made.
>
> It's not completely firm yet, it's just that Nobu had some code to  
> check
> in, and needed a name, and it's better to start with a long and  
> strange
> name and make it shorter if that's necessary than the other way round.

In my quick look at the source it seems that

	str.encoding

returns the current encoding of str.  So my own POLS would suggest

	str.encoding = "binary"

to change the encoding.  It just seems completely non-Ruby-like
to have:

	str.force_encoding("binary")

Gary Wright