Forums Feature Suggestions $iif error improve

Hello,

I have about 15 scripts with about 100+ more $iif identifier into my scripts and at one point one $iif return me an error how can i know where it is the error in which line or in which file it is

now is : * Invalid format: $iif

i wonder if can be like this: * Invalid format: $iif (line 100, script1.mrc)

- Thanks!

Supported simply due to the fact that this would maintain consistency with most of the other error messages.

i did not understand what u mean

Your suggestion would simply make the method of error reporting for $iif match that of other commands (like $read), thus I support it.

Hopefully you understand this, or a translator will give a decent translation.

I'm fairly sure that this issue exists in other identifiers/commands as well, though I cannot recall any from the top of my head.

Yeah, there are others missing error messages when used incorrectly or with errors that don't help track down the problem. One example is $base() if you use incorrect base types. It doesn't give you an error message other than whatever error may result in it being $null (such as when used as the only item in an echo). For example, $base(1000,50,10). For that matter, it does accept certain base types that aren't really valid (such as 19), though I suppose that just allows for potential new base types. It also does allow for an alphanumeric base conversion, which can be useful even if it doesn't allow for case sensitivity while doing so. So I guess allowing unusual base types if okay... it's just that the ones that aren't allowed don't throw any errors.

There are a variety of others as well that could use improved error reporting.

Yes there are more, from now i find the $iif , $base , $read as reported before by other users.