vulpineawoo/solanum
1
0
Fork 0
Code Issues Pull requests Projects Releases Wiki Activity

Message handlers should return void.

Browse source 
Also fix up some return values and stuff to use bool (or void if
nothing). I just did it whilst I was here.

According to jilles, the return value used to signify whether or not the
client had exited. This was error-prone and was fixed a long, long time
ago, but the return value was left int for historical reasons.

Since the return type is not used (and has no clear use case anyway),
it's safe to just get rid of it.
This commit is contained in:
Elizabeth Myers 2016-03-09 01:37:03 -06:00
parent eeabf33a7c
commit 3c7d6fcce7
99 changed files with 1339 additions and 1691 deletions
Download patch file Download diff file Expand all files Collapse all files

8
modules/m_ison.c
View file

@ -39,7 +39,7 @@
static const char ison_desc[] = "Provides the ISON command to check if a set of users is online";
static int m_ison(struct MsgBuf *, struct Client *, struct Client *, int, const char **);
static void m_ison(struct MsgBuf *, struct Client *, struct Client *, int, const char **);
struct Message ison_msgtab = {
"ISON", 0, 0, 0, 0,
@ -63,7 +63,7 @@ static char buf2[BUFSIZE];
* format:
* ISON :nicklist
*/
static int
static void
m_ison(struct MsgBuf *msgbuf_p, struct Client *client_p, struct Client *source_p, int parc, const char *parv[])
{
struct Client *target_p;
@ -81,7 +81,7 @@ m_ison(struct MsgBuf *msgbuf_p, struct Client *client_p, struct Client *source_p
len = strlen(buf);
current_insert_point = buf + len;
/* rfc1489 is ambigious about how to handle ISON
/* rfc1459 is ambigious about how to handle ISON
* this should handle both interpretations.
*/
for (i = 1; i < parc; i++)
@ -120,6 +120,4 @@ m_ison(struct MsgBuf *msgbuf_p, struct Client *client_p, struct Client *source_p
*current_insert_point2 = '\0';
sendto_one(source_p, "%s", buf);
return 0;
}