But then if there is a real error in the syntax it becomes harder to spot.
I'd much prefer ambiguous code to present errors rather than have mIRC bending over backwards to accommodate poor coding. That way everyone wins: code is faster and more readable, and scripters making genuine errors can quickly find them.
I don't see how handling this error would change error messages for those people that already use ()...
Also, Take this for example..
alias bug while $for(4) bad_command
This /bug returns the error...
/while: invalid format
I think this second one should be a bad command (message from the server)...
Edit: I also can not see how this would reducing the speed of the parser when using () or {}, since this condition is only evaluated when missing () or {}. It might even speed it up, generating other errors earlier...
Edit2: Let also face the fact that the parser, even now, doesn't always return the most meaningful indication of the actual error.
