fix: use correct number for INT_MAX (#21951)

Actually use INT_MAX rather than a number to prevent these types of
situations to begin with.
This commit is contained in:
dundargoc 2023-01-22 23:08:38 +01:00 committed by GitHub
parent 8e52d8a394
commit e5a537c885
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23

View File

@ -886,7 +886,7 @@ int ins_typebuf(char *str, int noremap, int offset, bool nottyped, bool silent)
// often.
int newoff = MAXMAPLEN + 4;
int extra = addlen + newoff + 4 * (MAXMAPLEN + 4);
if (typebuf.tb_len > 2147483674 - extra) {
if (typebuf.tb_len > INT_MAX - extra) {
// string is getting too long for 32 bit int
emsg(_(e_toocompl)); // also calls flush_buffers
setcursor();