projects / rbot / commit
? search:
summary | shortlog | log | commit | commitdiff | tree
(parent: 32f53f6) | patch
applied patch from ticket #15, and added .inspect to try and work out what
authorTom Gilbert <tom@linuxbrit.co.uk>
Wed, 24 Aug 2005 19:12:14 +0000 (19:12 +0000)
committerTom Gilbert <tom@linuxbrit.co.uk>
Wed, 24 Aug 2005 19:12:14 +0000 (19:12 +0000)
commit1fd21891fde8e97cb91941c32f7e49c4f4881fa7
treefd0b47f2a7a78c4751aaa88077f449ed8ddce7a7tree | snapshot
parent32f53f6a17396a8828c30c58ce8545c93c04ff2ccommit | diff
applied patch from ticket #15, and added .inspect to try and work out what
exception "reset by peer" gives you.

One thing I'm finding troublesome with ruby is working out what exceptions
things are going to throw. Especially poorly documented stuff implemented in
C. Why the Socket module throws an exception for "reset by peer" which
*isn't* a SocketError I don't know, but apparently it does.
bin/rbot diff | blob | blame | history
lib/rbot/ircbot.rb diff | blob | blame | history
tango_'s rbot development tree