Jeremy Shaw
1. The library is based around the old String based irc library. Would be nice to upgrade to something that used ByteStrings+Text+Builder. Practically speaking.. it's IRC. The maximum line length is 510 characters, and the bot typically needs to handle, at most, a few messages per second. So, space and time issues would only be a practical concern if your bot is joining hundreds of channels. But, that is no excused not to use Text :) Perhaps the fastirc library?
Hello there, I'm the author of the fastirc library. Even though it does address the problem of the old String-based 'irc' library, I wouldn't say that I'm very happy with the way it works. The library is a product of my early attempts to write fast, secure networking code in Haskell back in spring 2010. The protocol parser is based on attoparsec and is fast, but it doesn't work the way I would like it to work. It has a somewhat fragile way to ensure that lines don't get too long. Another shortcoming is the very weak session code, so if you want to use fastirc, you should only use the parser. I have started a new library based on attoparsec and the enumerator library, which is faster and handles line splitting properly with an enumeratee (that one is already on Hackage in the 'netlines' package). Also it will have good support for sessions using an FRP approach with the netwire library. However, be prepared to wait one or two weeks, until I have time to reach a point, where I can make an official release. Greets, Ertugrul -- nightmare = unsafePerformIO (getWrongWife >>= sex) http://ertes.de/