Forums Bug Reports error with /splay and a strange behavior...

1) If you tring to play a file that is not supported by mIRC (a .mpg or a .txt for exemple), mIRC said that the file doesn't exists :

You can reproduce this by typping something like :

Maybe mIRC can display that he can't open the file

2) Exemple is better that my bad explanation :] :









Edit : tested on 6.3 and 6.21

about the while loop problem, i'm not sure you can really call it a bug. it's how i'd expect it to behave :P for example:



the second operand in that condition is the string "12)". there's no opening ( so that closing parenthesis is treated as plaintext

now when you use <= with non-numbers, it no longer performs a numeric comparison, but rather a comparison based on the order of the ASCII values of the two operands. 2 is seen as greater than 12) because the ASCII value of 2 is greater than the ASCII value of the first character of 12)

the same thing occurs with the rest of your examples. should this be considered a bug? i don't think so :P a similar situation arises with evaluation brackets, if you have no opening evaluation bracket, a closing one is plaintext:

agreed with jaytea. you're thinking of the brackets in the context of your own code-- for mIRC to actually understand that "while %x < 1)" was a syntax error it would require mIRC to also know that you meant "1" and not "1)"-- and since mIRC does not expect strings inside quotes, there is no way of knowing. this is why it will only parse )'s if the condition began with a (. this is by design, and very much expected, or someone else would come here complaining, saying:

"
hey guys, while is acting weird!

while %prefix isin a. a: a) { echo -a hi }
"

Stick to the proper syntax rules defined by mIRC (dot your i's, cross your t's, and read http://kthx.net/ftb/#34 ) and you will be fine. Playing on the edge cases of the interpreter will likely lead you into trouble.

... as for the splay thing, I agree that mIRC should mention it cannot read the file, not pretend it does not exist.

Hum, you're right.
I always forgot that non-numeric values can be used in most of the cases with mirc

Thanks the /splay issue has been fixed for the next version.

Hum on mIRC 6.31, the /splay command doesn't give an error message when the file isn't supported by mIRC, since there was an error message in previous version about this behavior, you've seen this and *fixed it* but it would be nice to have the error message, it's better to one than nothing

If I try to use /splay to play a file that mIRC cannot play, eg. readme.txt, mIRC reports * /splay: unable to play 'readme.txt'. Are you not seeing that message?

The error is seen here in 6.31 if sounds are enabled in the options dialog, otherwise nothing .. as expected.

sorry about that