Re: Re: IRC
Some updates on that TODO, I was incorrect on two counts.
cl-irc *does* have a BSD/MIT style license. Hurray. I don’t know why I was under the impression it was otherwise.
snirc now does the [number] -> [string] mappings I wanted, such that the server sending, say, numeric reply 001 will result in snirc:conn-command being “RPL_WELCOME”.
snirc:cconnect does make more sense seperate from the read loop. It is sensible to expect the user to wish to be able to do something like (snirc:join conn “#Some_Channel”) between connecting and entering the read loop. As such, snirc:cconnect has been renamed to snirc:open-connection! and snirc:disconnect has been renamed to snirc:close-connection!.
Also, I won’t be modifying the default handlers to serve as examples. I’m going to be writing general documentation as well, which would be a better place for such examples. Ideally, the the general and API documentation should be well enough that the user has no reason to ever look at snirc’s code for reasons other than curiosity. I want it to work perfectly fine as a ‘black box’, as really a library should.
Also, I will likely be submitting some patches to the tcpip snowball, for things such as Chez/SCM support, flushing buffers, just returning #f instead of calling error or exceptions or whatever when a socket can’t be created (this one will be hard, but I’ve found the code to do for mzscheme at least), and such like.
No comments yet.