Does it "fail" or just return false? Try using it after the require. (This is a known RubyGems issue.)
James Edward Gray II
···
On Mar 10, 2006, at 3:08 PM, Sky.Yin@gmail.com wrote:
The require failure only occurs in IRB.
Most of it is just interface or the new headers feature (FasterCSV::Row). FasterCSV.shift() is the entire parser. It should be commented well enough to make sense of, I hope.
You could also read the thread on Ruby Core that spawned it, for further insight. Here's my first post in it:
http://ruby-talk.org/cgi-bin/scat.rb/ruby/ruby-core/6471
Feel free to ask questions if you have them...
James Edward Gray II
···
On Feb 27, 2006, at 7:45 PM, Sascha Ebach wrote:
I just had a look into the FasterCSV class and I must admit that I didn't expect such a large and highly engineered class.
Hi James,
One of my design goals is keeping FasterCSV pure Ruby. This makes it trivial to bundle with you app, if needed, and makes it more fun for me to maintain.
If you want to build a C version though, best of luck to you.
No, I certainly don't want to build a complete C version. I was thinking more like *if* RubyInline is installed, the main loop could be translated to C. That's all. So the C version would be completely optional. You know, if it is there use it else go with the default Ruby only. The question is how much faster can it actually be? If I look at PA's benchmark it looks like what you did is make it 10 times faster. But the Python version is still 10 times faster. Maybe it's possible to make FasterCSV like 2-3 faster with the use of RubyInline.
Saša Ebach
It returns a 'false'. and "require 'forwardable'" returns the same
'false' as well in IRB. Other dependant modules used by FasterCSV are
fine. Thank you for telling me that issue, which does confuse me for a
while.
James Edward Gray II wrote:
···
On Mar 10, 2006, at 3:08 PM, Sky.Yin@gmail.com wrote:
> The require failure only occurs in IRB.
Does it "fail" or just return false? Try using it after the
require. (This is a known RubyGems issue.)James Edward Gray II
Patches welcome. 
James Edward Gray II
···
On Feb 28, 2006, at 6:12 AM, Sascha Ebach wrote:
Hi James,
One of my design goals is keeping FasterCSV pure Ruby. This makes it trivial to bundle with you app, if needed, and makes it more fun for me to maintain.
If you want to build a C version though, best of luck to you.No, I certainly don't want to build a complete C version. I was thinking more like *if* RubyInline is installed, the main loop could be translated to C. That's all. So the C version would be completely optional. You know, if it is there use it else go with the default Ruby only. The question is how much faster can it actually be? If I look at PA's benchmark it looks like what you did is make it 10 times faster. But the Python version is still 10 times faster. Maybe it's possible to make FasterCSV like 2-3 faster with the use of RubyInline.
Patches welcome.
if I can do it I will. But don't hold your breath
Saša Ebach