| Age | Commit message (Collapse) | Author |
|---|
|
|
|
|
|
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.
|
|
|
|
* Tweaked the debug() stuff a bit. Need to do this more cleanly really
* Added a fair bit of documentation for some of the new features
|
|
* Added french language file (TODO most of the plugins just talk english)
* The way the Enum configs were set up, it wasn't possible to add language
files to rbot at runtime (the directory was only scanned at startup). Now
you can set a values Proc, which is called to return a list of allowed
values whenever it's queried.
* Added Config module for determining where we were installed.
Unfortunately rubygems is a total whore in this regard, and I hope the
current hackery I have to do to support it becomes redundant in the
future.
|
|
* Added Rakefile, tweaked gemspec
|
|
* Updated docgen to generate rdoc again with the new repo structure
* added new restart command to the core bot, quits irc and reexecs the
bot, to pick up new code/libraries etc.
|
|
* Reworked the Timer module. The Timer now has a smart thread manager to
start/stop the tick() thread. This means the timer isn't called every 0.1
seconds to see what needs doing, which is much more efficient
* reworked the ircsocket queue mechanism to use a Timer
* reworked the nickserv plugin to use maps
* made server.reconnect_wait configurable
* added Class tracing mechanism to bin/rbot, use --trace Classname for
debugging
|
|
|
|
|
|
|
|
|
|
|
