Which Error Return Is Best

[Melba23]

Chimaera,

we should always set a return in a func

Not at all! This was just an example of using the SetError function to return user-specified values in the return, @error and @extended locations. The values themselves are just indications - I attach no particular importance to 77 (everyone knows the real value should have been 42 ); 77, 99, and "Wrong" were just placeholders to fill out the function parameters.

However, I do believe that the use of SetError is a vital part of the coder's armoury - particularly in complex scripts. If you take a look inside some of my UDFS you will see how I have used it to return useful information when a function fails for some reason. Here is an example from the _GUIExtender_Section_Extend function within GUIExtender:

; Return values .: Success:  Returns 1
;                  Failure:  Returns 0 and sets @error as follows:
;                  1 = Invalid section ID (@extended: 1 = not in array, 2 = no _Start function used)
;                  2 = Section already in required state
;                  3 = GUI minimized

So the user can very quickly find out why the UDF did not run as expected which could cut down on the debugging time quite a bit.

Clearer now?

M23

[BrewManNH]

Sorry im confused now so were saying 1 isnt valid now?

1 is only a valid return if that's what you decide is a valid return for your function. There is 1 and only 1 default return value from a function and that is zero. Everything else returned from functions is decided by you (if you write the function) or the person that wrote the function.