Forums Bug Reports Error .. But not show the error line ..

on *:TEXT:*:#Channel:If ($nick isreg) echo is reg
Show only "* /if: invalid format"
Where is the line ? I think this is a bug ..

"* /if: invalid format (line 3, script24.mrc)"
Show the error line fine ..

That type of error is at all erroring if .. I mean ..
on 1:TEXT:*:#: If ($nick =) echo is test
on 1:TEXT:*:#: If ($nick !=) echo test
on 1:TEXT:*:#: If ($nick isreg) echo is reg
on 1:TEXT:*:#: If ($nick isop) echo is reg
... All this don't return the line of the error ..

And other command what donne an error .. The parser don't show the line ..
on 1:TEXT:*:#: WhatEver what donne error

well, for starters you may try /help if-the-else because your obviously unknowledgable of the proper syntax. And just to give you an idea, the conditions your trying require a second parameter such as "if ($nick isreg)" SHOULD be "if ($nick isreg $chan)"

As for the line number, why should it return a line number. You know what you just edited, look there. Do you always make 100 line edits inbetween trials?

My examples is intentional bugie for showing what parser don't show the error line .. Heh reread pls ..

I believe I already commented on that k thnx

Anyway its a bug

what do u mean i dont under stand please reply

on 1:TEXT:*:#: If ($nick isreg) echo is reg -
the parser don't show number of the error line .. i mean that is a bug ..

How is that a bug, if that same message has made its way all the way up to 6.03 If it was relevant enough to fix, it would have been fixed versions ago. And besides, why should a compiler have to output a line number for your stupidity. If you knew the socrrect syntax in the first place, we wouldn't be having this discussion.

Yes, definitely a bug. I think it was reported earlier though.

The point is not whether Adrenalin is knowingly using imporper syntex... he was using those as mere examples. His case and point is that mIRC doesn't show the $scriptline that the error occured on if the script only takes up one line. (assuming that is the exact cause of the bug, it may be other syntex related... but that's for Khaled to pin down.)

It's still a bug none the less, and may effect an unwitting user in the future.

- Raccoon

It's the $scriptline bug posted here.

It should also be noted that this only happens in single-line events, $scriptline in mutli-line events and single-line aliases works just fine.