Age | Commit message (Collapse) | Author |
|
|
|
|
|
Apparently on some systems, subsquent connect() calls may fail with EISCONN
error, to indicate that the connection succeded in the background, instead
of returning 0.
|
|
|
|
|
|
|
|
|
|
The error is handled using the return value
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
This reverts commit e3b91475ffd7c1c76868964614f66060ba9e3a85.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
fixes #2436
|
|
|
|
|
|
|
|
The number of arguments is not always the same
|
|
|
|
|
|
|
|
Also remove the duplicate send_self_join methods, user only send_user_join
|
|
CHANMODES and PREFIX only
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
By fixing a namespace when looking for an XML element containing that message
|
|
|
|
By removing invalid chars, see http://www.w3.org/TR/xml/#charsets
|
|
|
|
|