RE: [PEAR-DEV] Competing IRC Class - Yapircl - Yet Another PHP IRC Library

Well step one would be to determine what the differences are between the packages .. If I understood this correctly, competing packages should only live in PEAR if they take a fundamentally different approach. If they do things the same way they should rather be merged. Regards, Lukas Smith smith@dybnet.de _______________________________ DybNet Internet Solutions GbR Reuchlinstr. 10-11 Gebäude 4 1.OG Raum 6 (4.1.6) 10553 Berlin Germany Tel. : +49 30 83 22 50 00 Fax : +49 30 83 22 50 07 www.dybnet.de info@dybnet.de > -----Original Message----- > From: LIMBOURG Arnaud [mailto:arnaud.limbourg@cegetel.fr] > Sent: Tuesday, December 17, 2002 10:59 AM > To: Geir Torstein Kristiansen; pear-dev@lists.php.net > Subject: RE: [PEAR-DEV] Competing IRC Class - Yapircl - Yet Another PHP > IRC Library > > Did not look at the code but i'd say it could fit under Net_YAPIRC > > Arnaud. > > > Hi. I am the developer of Yet Another PHP IRC Library. I have > > been lurking on > > the pear IRC channel and the mailinglists for some time now > > and since the > > recent announcement of a competing IRC class I feel the need > > to come out of > > the closet with my project as there might be namespace issues etc:) > > > > Consider this a request for comments. I will be happy to move > > the development > > to the PEAR cvs should you feel the quality is sufficent. > > > > http://projects.gtk.mine.nu/yapircl > > > > > > http://projects.gtk.mine.nu/archive/yapircl/yapircl-0.5.7.tar.gz > > http://home.online.no/~geir37/archive/yapircl/yapircl-0.5.7.tanˆ
×dž > > Ws^ÓÊ9¿W > > r.gz (mirror) > > > > Status > > It is close to feature complete and should be stable, the > > longest running > > YapirclBot based client I know of has been running for 40 days. > > > > Status win32 > > There were issues with nonblocking sockets in the socket > > extension on that > > platform the last time I tested, I tried commenting out those > > calls and it > > worked. > > > > <rant> > > > > Plans > > What I feel remains is a rewrite to handle multiple > > connections better by > > allowing multiple connections to be made from within the same Yapircl > > instance. > > > > I am considering separating out the guts into an irc > > connection object and dcc > > connection object which will be handled inside the main > > Yapircl object. This > > master object will then deal with the select()ing etc. This > > is not totally > > trivial as it might affect the current API because Yapircl is used by > > subclassing it and adding callbacks so I would need to find a > > solution to > > this. The timer system would also have to be modified. > > > > I could rewrite it even more to make objects for users, > > channels and whatever. > > However as I see it a lot of "traversing an array of objects" > > issues are > > avoided with the current use of associative arrays with keys > > I am somewhat > > wary of rewritting all of this just to use an object in > > places there are > > might be no appearant advantages to use objects and might > > complicate the > > usage of the library. > > > > This has been a learning experience for me and is probably my > > largest software > > project yet so I'm very open to suggestions. > > > > </rant> > > > > -- > > Geir Torstein Kristiansen > > > > web: http://projects.gtk.mine.nu > > > > > > -- > > PEAR Development Mailing List (http://pear.php.net/) > > To unsubscribe, visit: http://www.php.net/unsub.php > >