texlive[50517] Build/source/texk/makeindexk: increase ARGUMENT_MAX to

[commits+karl at tug.org]

Revision: 50517
          http://tug.org/svn/texlive?view=revision&revision=50517
Author:   karl
Date:     2019-03-21 23:38:30 +0100 (Thu, 21 Mar 2019)
Log Message:
-----------
increase ARGUMENT_MAX to 10240 (from 1024)

Modified Paths:
--------------
    trunk/Build/source/texk/makeindexk/ChangeLog
    trunk/Build/source/texk/makeindexk/mkind.h

Modified: trunk/Build/source/texk/makeindexk/ChangeLog
===================================================================
--- trunk/Build/source/texk/makeindexk/ChangeLog	2019-03-21 22:35:15 UTC (rev 50516)
+++ trunk/Build/source/texk/makeindexk/ChangeLog	2019-03-21 22:38:30 UTC (rev 50517)
@@ -1,3 +1,8 @@
+2019-03-21  Karl Berry  <karl at tug.org>
+
+	* mkind.h (ARGUMENT_MAX): increase to 10240 from 1024,
+	since can be used with glossaries, etc. Found by Nicola Talbot.
+
 2015-07-10  Peter Breitenlohner  <peb at mppmu.mpg.de>
 
 	* Makefile.am: Better dependencies for 'make check'.

Modified: trunk/Build/source/texk/makeindexk/mkind.h
===================================================================
--- trunk/Build/source/texk/makeindexk/mkind.h	2019-03-21 22:35:15 UTC (rev 50516)
+++ trunk/Build/source/texk/makeindexk/mkind.h	2019-03-21 22:38:30 UTC (rev 50517)
@@ -3,7 +3,7 @@
  *  This file is part of
  *	MakeIndex - A formatter and format independent index processor
  *
- *  Copyright (C) 1998-2012 by the TeX Live project.
+ *  Copyright (C) 1998-2019 by the TeX Live project.
  *  Copyright (C) 1989 by Chen & Harrison International Systems, Inc.
  *  Copyright (C) 1988 by Olivetti Research Center
  *  Copyright (C) 1987 by Regents of the University of California
@@ -302,19 +302,13 @@
 consistent, or reasonable!  Therefore, change them only with great
 care.
 
-The array sizes should be made generously large: there are a great
-many uses of strings in MakeIndex with the strxxx() and sprintf()
-functions where no checking is done for adequate target storage sizes.
-Although some input checking is done to avoid this possibility, it is
-highly likely that there are still several places where storage
-violations are possible, with core dumps, or worse, incorrect output,
-ensuing.
+If any array overflows, please report to tex-k at tug.org.
 ======================================================================*/
 
 #define ARABIC_MAX    99	/* maximum digits in an Arabic page */
 				/* number field */
 
-#define ARGUMENT_MAX  1024	/* maximum length of sort or actual key */
+#define ARGUMENT_MAX  10240	/* maximum length of sort or actual key */
 				/* in index entry */
 
 #define ARRAY_MAX     1024	/* maximum length of constant values in */