syntax error is a error and then it's obvious for it to throw an error.
not sure why you would want it to misbehave like it now does...

and if the current behavior is not confusing, I don't know what is.
as currently, one needs to re-read the whole script to find mistyped macro without even knowing that he has one.

there is no excuse to leave it like it is.