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 know I posted this in the bugs sections, I am sorry)

I second this.

This feature would not be usefull in this form. It needs to be expanded, like this:

Have an identifyer return the script name that the error occured in.

Have an identifyer return the line that the error occoured in.

and so-on

This would be usefull for the larger scripts so people dont need the error goto in every little event and alias.

I think the best thing to do would be add an error event aswell as $error, and have 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.

Personally id just like a /resume or /resumenext or /resumeat

I have used /resumenext to just crash my way down to something that works (pretty rude but sometimes its better than stopping altogether)

I'd like a /raiseerror command, an alternative to returning from or halting the current alias if required conditions for it's operation are not met. /raiseerror could abort the current alias, not going to the error handling for that alias.
(edit)
But I suppose this thread is too far back to get much notice for new suggestions?

No, a lot of people have forum threads set to show the most active in the past 2 weeks (or another short space of time) so even if a thread is 6 months old (or more) if someone replies to it, they can see that it has been replied to. And 3 days really doesn't make it that inactive :-)

You can set your Forum options by going to the "My Home" link at the top, scroll down and click on 'Edit' next to the words "Display preferences, number of shown threads, languages, colors...".

Have fun!

Regards,