I would like to learn...

[FrancescoDiMuro]

Hi guys! Sorry fot the click-bait title ( not really ) I'd like to learn when to use @error, and, what is error checking? I'm almost new at this language ( about 5 months since my first use ) and, I'd realluy be very happy if someone can explain to me those things... I'd like to be master of programming, and you guys ( water and so on ) are really powerful Master Hope you guys have a good day! Francesco 

PS: a in-depth guide would be very nice!

Edited November 21, 2016 by FrancescoDiMuro

[JLogan3o13]

We have not one but two in-depth guides, the help file and a Wiki. Both go into great detail about @error, have you read through them?

https://www.autoitscript.com/autoit3/docs/

https://www.autoitscript.com/wiki/Main_Page

 

[mikell]

  On 11/21/2016 at 3:12 PM, FrancescoDiMuro said:

about 5 months since my first use

Expand  

... and you still don't know what @error is and what error checking means ?! 

OMG 

[FrancescoDiMuro]

  On 11/21/2016 at 3:17 PM, JLogan3o13 said:

We have not one but two in-depth guides, the help file and a Wiki. Both go into great detail about @error, have you read through them?

https://www.autoitscript.com/autoit3/docs/

https://www.autoitscript.com/wiki/Main_Page

 

Expand  

I'm a lovely user of the Help file! It's very useful ( maybe it was intended for a different use? Jk ahahahah ). Thanks for the reply by the way. I was wondering on something about "How to build a program "efficently"", well-ordered, readable... I like to write code in this way... Are there any rules about that? Something like divide the "main" program in more functions... And, does the main exist in AutoIt? Thise kind of rules... I want to know, please I like this language, and I want to learn!

[JLogan3o13]

The wiki has a very nice page on Best Practices

[FrancescoDiMuro]

  On 11/21/2016 at 3:24 PM, mikell said:

... and you still don't know what @error is and what error checking means ?! 

OMG 

Expand  

Unfortunately I can't study this language every day... I know what is error, but Idk when to use it... What's error checking? This kind of things...

[mLipok]

https://www.autoitscript.com/wiki/Best_coding_practices

 

[JLogan3o13]

  On 11/21/2016 at 3:24 PM, mikell said:

... and you still don't know what @error is and what error checking means ?! 

OMG 

Expand  

Not helpful to a new person. He may have used it once 5 months ago and is just now coming back to it. We're here to encourage people

[FrancescoDiMuro]

  On 11/21/2016 at 3:26 PM, mLipok said:

https://www.autoitscript.com/wiki/Best_coding_practices

 

Expand  

About @error, any function returns different @errors and different numbers of it... So, If I had to be meticulous, I should check what kind of error it is, or not? Thank you

[FrancescoDiMuro]

  On 11/21/2016 at 3:26 PM, JLogan3o13 said:

Not helpful to a new person. He may have used it once 5 months ago and is just now coming back to it. We're here to encourage people

Expand  

Thanks... I didn't say anything... But I didn't share his pov... I'm here for learning If you ( mikell ) wanna teach me... I'm here  

Edited November 21, 2016 by FrancescoDiMuro

[mLipok]

  On 11/21/2016 at 3:30 PM, FrancescoDiMuro said:

About @error, any function returns different @errors and different numbers of it... So, If I had to be meticulous, I should check what kind of error it is, or not? Thank you

Expand  

You should not, to step over without doing nothing, for this reason you should check each error and make a decision what program should do in next step.

 

[FrancescoDiMuro]

  On 11/21/2016 at 3:34 PM, mLipok said:

You should not, to step over without doing nothing, for this reason you should check each error and make a decision what program should do in next step.

 

Expand  

I was thinking something like... Take i.e. _FileCreate... The function returns 2 different kind of @error... So, if I want to be meticulous, I'd check something like:
 

If @error = 1 Then
    DoSomething...
Else If @error = 2 Then
    DoSomethingElse...
End If

You were meaning something like this? Because I were  

[JLogan3o13]

At its simplest, yes, that is the way to go about it. Down the road as you are more comfortable there are ways to streamline that, but I would stick with the format while you're getting your feet wet.

[mLipok]

Please try to use AutoIt syntax:

If @error = 1 Then
    DoSomething...
ElseIf @error = 2 Then
    DoSomethingElse...
EndIf

You do not must always be such  meticulous .
You just must to check @error to make sure you do not do much more errors (Snowball effect).
But this is good point to know what the issue is and solve them later, so you should check errors and log them in any way, as a first step do solve the problem.

_Example()
Func _Example()
    ........
    _SOME_FUNCTION()
    If @error Then 
        ConsoleWrite('! ---> @error=' & @error & '  @extended=' & @extended & ' : MY DESCRIPION' & @CRLF)
        Return .....
    EndIf
    ........
EndFunc

 

EDIT: btw you should some how interact with EndUser, so you must show to him any state of progress, this mean also you should say to him that program not finish the job correctly , because something happend .

Edited November 21, 2016 by mLipok

[FrancescoDiMuro]

  On 11/21/2016 at 3:48 PM, mLipok said:

Please try to use AutoIt syntax:

If @error = 1 Then
    DoSomething...
ElseIf @error = 2 Then
    DoSomethingElse...
EndIf

You do not must always be such  meticulous .
You just must to check @error to make sure you do not do much more errors (Snowball effect).
But this is good point to know what the issue is and solve them later, so you should check errors and log them in any way, as a first step do solve the problem.

_Example()
Func _Example()
    ........
    _SOME_FUNCTION()
    If @error Then 
        ConsoleWrite('! ---> @error=' & @error & '  @extended=' & @extended & ' : MY DESCRIPION' & @CRLF)
        Return .....
    EndIf
    ........
EndFunc

 

Expand  

What about AutoIt synthax? What I wrote wrong? By the way... I was meaning just this! What is Snowball effect? Where I can find those things? And... Should I create a log for each program I do? Thanks buddy!  

[mLipok]

Else If should be ElseIf

End If should be EndIf

 

[mikell]

You could begin using this, usually it's enough

If not @error Then   ; means no problem, @error = 0
      DoWhatShouldBeDone
Else    ; there was a problem, @error <> 0
      CallRescueDepartment
EndIf

 

[mLipok]

  On 11/21/2016 at 3:50 PM, FrancescoDiMuro said:

What is Snowball effect?

Expand  

Stand on a hill, throw a small ball of snow, see what will be on the bottom.
A disaster.

[FrancescoDiMuro]

  On 11/21/2016 at 3:52 PM, mLipok said:

Else If should be ElseIf

End If should be EndIf

 

Expand  

Ah, thank you Yeah, I wrote it fast... And I didn't pay attention about it Sorry for that... And about the snowball effect and about the errors' log?  

[mLipok]

  On 11/21/2016 at 3:53 PM, mikell said:

You could begin using this, usually it's enough

If not @error Then   ; means no problem, @error = 0
      DoWhatShouldBeDone
Else    ; there was a problem, @error <> 0
      CallRescueDepartment
EndIf

 

Expand  

Personally, I prefer the reverse order.
First, check if something is wrong, and finally do what you need.

I mean:

If @error Then   ; there was a problem, @error <> 0
      CallRescueDepartment
Else    ; means no problem, @error = 0
      DoWhatShouldBeDone
EndIf

 

This is particularly useful when creating functions for the UDF, then do not forget about this code to work flawlessly.
But this is only my feeling