philippelh/bitchx
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Bump MAXPARA (maximum protocol message arguments) to 20 as per EPIC5

Browse Source 
Needed to bump it to 16 anyway (the RFC says 15 plus the protocol command itself, so 16), but EPIC5 bumped it
up to 20 based on a report from users of RusNet so we might as well go up to that as well.
This commit is contained in:
Kevin Easton
2019-06-26 17:26:02 +10:00
parent 0cbf8014ff
commit 6ef78086f8
2 changed files with 3 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files

2
Changelog
View File

@@ -1,5 +1,7 @@
[Changes 1.2.2] [Changes 1.2.2]
* Bump MAXPARA (maximum protocol message arguments) to 20 as per EPIC5. (caf)
* Correctly handle a last argument prefixed with : for any protocol message, * Correctly handle a last argument prefixed with : for any protocol message,
for compatibility with inspircd. Reported by trn. (caf) for compatibility with inspircd. Reported by trn. (caf)

2
include/parse.h
View File

@@ -44,7 +44,7 @@ extern int doing_privmsg;
#define WAIT_BANS 1 #define WAIT_BANS 1
#define WAIT_MODE 2 #define WAIT_MODE 2
#define MAXPARA 15 #define MAXPARA 20 /* RFC1459 says 15+1, but RusNet uses more */
#endif /* PARSE_H_ */ #endif /* PARSE_H_ */