The point is that it is easy to forget something simple, such as the C parameter to /tokenize, and without any kind of error message telling you that you messed it up, you could end up just sitting there scratching your head and wondering why $1- keeps coming out $null. The C parameter should be required for mirc to continue with that command. I don't know about anyone else, but when I'm debugging code, I find that error messages make it easier to locate errors -- that's kind of what they're there for. But for a command to produce no error when it is obviously being used incorrectly (C is not optional as far as getting it to actually work is concerned) is just plain wrong, hence the bug report.
The person that brought this bug to my attention forgot the C parameter, which is a simple mistake that anyone can make. Also, if a user is passing a %variable or $identifier (maybe a misspelling of $asc(C)?) it might take a while to figure out what went wrong where a simple "* /tokenize: invalid parameters" would tell them right off where they should be looking.
Last edited by Hrung; 01/02/05 08:38 PM.
