From: "NARUSE, Yui" <naruse@...>
Date: 2010-02-19T05:22:27+09:00
Subject: [ruby-core:28240] Re: Removing Syck from ruby

Hi,

(2010/02/19 1:58), Aaron Patterson wrote:
> Having both syck and psych in ext is fine, except that both syck and
> psych provide Object#to_yaml.  When psych is imported to ext, I would
> like it to provide the implementation of Object#to_yaml.

I think, it is ok.

> I think removing Syck from ruby and shipping it as a gem is better than
> shipping two YAML parsers and emitters with Ruby.  In my opinion, it
> will be confusing to have two.  When someone writes:
> 
>   require 'yaml'
> 
> Which one will they use?  I'm afraid that if we ship syck *or* don't
> make psych default, no one will upgrade from syck.

Importing will be some steps, like:

1. import ext/psysh, but lib/yaml is still see ext/syck
2. replace lib/yaml, to use ext/psych
3. remove ext/syck

-- 
NARUSE, Yui  <naruse@airemix.jp>