On Jun 23, 7:55 pm, rohit <[email protected]> wrote:
> On Jun 23, 9:19 pm, Jeremy Evans <[email protected]> wrote:
>
> > On Jun 23, 6:49 pm, John W Higgins <[email protected]> wrote:
>
> > > Would it be possible to leave the current implementation within the core 
> > > of
> > > Sequel so that folks that can live with the current implementation don't 
> > > now
> > > require the csv library and then have the extension available to override
> > > the default implementation with the more advanced version?
>
> > > I'm not certain if this poses a maintenance issue for you or not......
>
> > Nope, that's not an issue.  We could leave the current to_csv in core,
> > and still have a extension that uses the csv library.
>
> > Jeremy
>
> Perhaps Sequel should use fastercsvhttp://fastercsv.rubyforge.org/in
> the extension?

Well, on ruby 1.9, csv is fastercsv.  I could see using fastercsv on
ruby 1.8, I guess.  In general, I prefer to use external libraries
only when there aren't suitable libraries in the stdlib (currently
active_model, nokogiri, json, and tzinfo).  The main benefit of
fastercsv on 1.8 is that it is faster (I'm guessing).  Are there other
benefits to fastercsv over csv on 1.8?

Jeremy

-- 
You received this message because you are subscribed to the Google Groups 
"sequel-talk" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to 
[email protected].
For more options, visit this group at 
http://groups.google.com/group/sequel-talk?hl=en.

Reply via email to