I think this is not a very useful function.
For every alias in my script I will have to put a :erro and $error doesn´t give me the file name or the line were the error occurred.

The smartest thing you could do is add an error event, like:
on *:scripterror: {
echo -s Error found: $error
}

This would be usefull for people that have their scripts on the net and when an error occurs the users don´t know what to say because they cleared the text or there mirc closed down, and just say that something went wrong. With this, there could be an erro log created and the user would just send them the file.

I think the best thing to do would be add an error event aswell, and have them it triggered just 'above' the default error-handling. So when an error occurred it would go through these steps:
current alias' error jump-point code.
propagate through calling aliases' error-handling code.
call script error event(s).
mIRC's default error-handling code.

And of course allow /reseterror to halt the error-handling at any point. This way you can have alias-specific handling and/or generic handling.

Really this thread should be in Feature Suggestions though, since whether you like $error or not, you can't consider it a bug.

there is a easy solution to your wooes



Just dont have your code error.



<snicker snicker>