From: Nobuyoshi Nakada <nobu@...>
Date: 2007-11-16T23:07:53+09:00
Subject: Re: Iconv#iconv returning wrong object

Hi,

At Fri, 16 Nov 2007 18:13:36 +0900,
Dirk Traulsen wrote in [ruby-core:13594]:
> 1. 
> Iconv#iconv should return an array like Iconv.iconv and like it was 
> documented. (I would like to follow the 'spirit' of the documentation 
> here, which calls the method a shorthand of Iconv.open and collect and 
> such returning an array, even if it makes the error to give a wrong 
> interface, which needs to be corrected anyway.)

It breaks backward compatibility, and it doesn't make much
sense because they are not convertible.

> 2.
> Iconv#conv should be introduced as a new instance method of Iconv, 
> which returns a string using Array.join like the class method 
> Iconv.conv does today. (Iconv#conv would return consistently what 
> Iconv#iconv is now returning against the documentation and logic.)

Iconv#conv wouldn't have issues, I guess.

> What is the opinion on the list?
> Iconv needs to be changed anyway. So, is it better to be consistent or 
> not?

Could you tell the reason why it needs?

-- 
Nobu Nakada