On Mon, Nov 8, 2010 at 10:56 PM, Lars Dɪᴇᴄᴋᴏᴡ 迪拉斯 wrote:
>> What if I don't want it to use that "Encode" interface? I just want it to
>> be a module on its own.
> Any good reason for doing so? This goes against two expectations set up by
> CPAN precedent:
> • All modules that deal with encoding/d
> What if I don't want it to use that "Encode" interface? I just want it to
> be a module on its own.
Any good reason for doing so? This goes against two expectations set up by
CPAN precedent:
• All modules that deal with encoding/decoding are compatible with Encode.
• All modules in the Encode n
