On Fri, 19 Oct 2018 at 19:04, Peter Relson <rel...@us.ibm.com> wrote:
> There is no "should" in this sort of situation. There is a "could". There > is a "wouldn't it be nice if". > > Could it be done? Sure. Would having done so have helped this case? Sure. > Would doing so be a better use of limited resources than doing something > else? > > There is no requirement that a macro do any more than what it is > documented to do, which is to provide the correct expansion when you have > provided valid syntax. Most macros do far more than that. > I have inherited an extensive macro library where each API macro has an extra &X parameter to catch any excess positional operands and misspelled keyword operands. It's just a single internal macro to validate that &X is empty or complain otherwise. There is a lot of value in catching the mistake as early as possible. It saved me already several times, and I am sure it avoided pulling hairs in the decades since the investment was made. Rob
