[cpp.replace.general] Macro redefinitions that do not use the final ellipsis consistently

[Halalaluyafail3]

Full name of submitter (unless configured in github; will be published with the issue): Jay Ghiron

Reference (section label): [cpp.replace.general]/2

Issue description:

This issue is a duplicate of C Issue 1066. The current wording is insufficient to forbid the following macro definitions:

#define F(X)
#define F(X,...)

Suggested resolution:

Modify [cpp.replace.general]/2:

Likewise, an identifier currently defined as a function-like macro (see below) may be redefined by another #define preprocessing directive provided that the second definition is a function-like macro definition that has the same number and spelling of parameters, the two definitions agree in use of the final ellipsis, and the two replacement lists are identical, otherwise the program is ill-formed.

[BlowingWind314]

... is sometimes refered as a parameter, e.g. [cpp.replace.general]/5, 16

Otherwise, there shall be at least as many arguments in the invocation as there are parameters in the macro definition (excluding the ...).

The number of arguments so combined is such that, following merger, the number of arguments is either equal to or one more than the number of parameters in the macro definition (excluding the ...).

But parameters are explicitly specified by [cpp.replace.general]/13

The parameters are specified by the optional list of identifiers.

Maybe it's better to edit [cpp.replace.general]/13 to include ... as a parameter.