4 replies to this topic

[big_daddy]

This is something I'd like to have everyone's opinion on.

As of late it seems an emphasis on code size has overruled what I would consider proper error handling. What are your thoughts on this?

[jpm]

for 50k I prefer handle fatal error.
in fact the pb is not a autoit fatal error but a crash of autoIt

[Manadar]

Very interesting big_daddy.

I'm a fan of leaving the fatal error handling up to the programmer. Let the programmer decide where to look out for errors and capture them.

[Uten]

I have to been thinking a little about error handling in AutoIt lately. I have not thought it trough yet but I think I would like an option to register an error handler along the same lines you do for com objects would be an achievable solution. Maybe add a @functionid macro to identify the failing function. The custom error handler provided by the coder could look like this;

Func ErrHandler($err, $ext, $funcid, $line)
    MsgBox(48, "ERROR", "Error occured at line: " & $line" & @CRLF & "NOTE: I will terminate now..:(")
    ;Note : If the programmer odn terminate the application at this point it will continue as usual.
EndFunc
ƒo݊÷ Ø    Ýr‹¥u·®±çeŠG­†+ºÚ"µÍ‰ˆÌ͎ÛÛœ’[™ˆHœ›Ü’[™”™YÚÝŠ   œ][Ýќ’[™‰œ][ÝÊBŽÈÈ^HÝY™‚‘œ›Ü’[™”™YÚÝŠ ˆÌ͎ÛÛœ’[™ŠB

If ErrHandler is called with an empty string it is disabled.

You should still be able to use the @error and @extended macros as we do today.

Well that was my $0.02 on the topic. I'm sure the devs can find lots of cases where this approach will be impractical.

EDIT: Language typo

Edited by Uten, 12 June 2007 - 10:38 AM.

[Blue_Drache]

Even with larger code requirements, I believe in error handling on the part of the software's programmer. Case in point, my most recent monster has frankensteined to over 2100 lines, but it's not a complaint. A good 1/3 of the code is error checks. For this particular program, the error checks are necessary. If this was just for personal use, I'd not have near the If @error Then xyz EndIf statements.