• valid names like R, which are already reserved yet are permitted by LET();
• names with outer whitespace, which is invalid yet could go unnoticed in a call; and
• names with "injection characters" like ) and ,, which could alter the call when spliced.

• valid names like R, which are already reserved yet are permitted by LET();
• names with outer whitespace, which is invalid yet could go unnoticed in a call; and
• names with "injection characters" like , and ), which could alter the call when spliced.

Should I hard code these two exceptions into NameIsValid(), among the ElseIf filters that precede the Application.Evaluate()?

1. Should I hard code these two exceptions into NameIsValid(), among the ElseIf filters that precede the Application.Evaluate()?

2. Also, how might I improve the performance of NameIsValid(), given that it invokes Application.Evaluate()? Currently, it is even slower at scale than excel-names, which is already slow enough.

Background

Update

After examining the NameRulesUnicode64k.xlsm spreadsheet in excel-names, it appears that my NameIsValid() is in close agreement. When examining whether or not a single character is OK as a valid name, there are only 2 discrepancies across 65,535 characters:

While neither I nor the spreadsheet can vouch for names of greater length, I suspect this convergence will hold true in those cases too.

Question

Should I hard code these two exceptions into NameIsValid(), among the ElseIf filters that precede the Application.Evaluate()?

Background