Re: php-csv-parser

From: Date: Sat, 04 Oct 2008 01:01:13 +0000
Subject: Re: php-csv-parser
References: 1 2  Groups: php.pear.dev 
Request: Send a blank email to pear-dev+get-50824@lists.php.net to get a copy of this message
On 2008/09/30, at 3:55, Ken Guest wrote:
On Sun, Sep 28, 2008 at 9:44 AM, Kazuyoshi Tlacaelel Kanazawa <ktlacaelel@gmail.comwrote: I am a little unhappy with the csv parsers in the pear site. so I started something very simple from scratch in the last few hours and uploaded it as an open source project. I appreciate the energy that you are throwing into this but wouldn't it make more sense for you to channel it into the existing package rather than reinventing the wheel? That way you can take advantage of the existing test cases and documentation rather than having to write similar? You are planning on developing test cases and documenting your work aren't you?
I agree, I was thinking on expanding File_CSV not replacing it. tests & documentation? of couse! I am running phpunit 3.3.1 and want to wait a bit more to compile documentation. http://code.google.com/p/php-csv-parser/source/browse/trunk/test/results/text I saw some older version of phpunit tests in some packages do these run on pear? or is there any phpunit specific version to use?
I feel pear slows down the release process a little. does anybody share this thoughts? I have found, and this is not intended as a slight on you, that solutions that are released too quickly tend towards being incomplete, buggy and not very well documented. Because of this they then consume more time and energy to get into a useable state than if they were planned better and more time were spent on them between release cycles.
your right.
I like pear. I'm sorry but I'm really not getting this vibe from you. I think if you truly did like PEAR you would contribute some bug reports and perhaps some patches towards the project rather than taking the approach that you have done. Or at the very least you might use the PEAR coding standards!
Thanks Ken, I do brake some PEAR standards rules. and I understand that for PEAR those are crucial. those are to be refactored. I'll still say that I like pear, and want to note that my criticism comes with an effort of constructivism. and in a way I guess this is "the patch" and I am asking the community for guidance.
kind regards Ken
kindly accepted Best, Kazuyoshi Tlacaelel.

« previous php.pear.dev (#50824) next »