is that multithread? Are there any disadvantages In this method?

[Guest]

I think I found some method to run more then one loop at the same time and also use Sleap(1000) Without slowing down these loops:

 

HotKeySet("{ESC}","Exit1")

AdlibRegister("Loop1",100) ; loop that sleap 100 Milliseconds
AdlibRegister("Loop2",100) ; loop that sleap 100 Milliseconds

ConsoleWrite("      Sleep 1 <---------------------------------------------------------------------------" & @CRLF)
Sleep(1000)
ConsoleWrite("      Sleep 2 <---------------------------------------------------------------------------" & @CRLF)
Sleep(1000)
ConsoleWrite("      Sleep 3 <---------------------------------------------------------------------------" & @CRLF)
Sleep(1000)
ConsoleWrite("      Sleep 4 <---------------------------------------------------------------------------" & @CRLF)

For $a = 5 To 15
    Sleep(1000)
    ConsoleWrite("      Sleep "&$a&" <---------------------------------------------------------------------------" & @CRLF)
Next

While 1
    Sleep(1000) ; I am sleaping 1000 Milliseconds!!
WEnd

Func Loop1()
    ToolTip("Loop1") ; And at the same time I sleaping 100 Milliseconds
EndFunc   ;==>Example


Func Loop2()
    ConsoleWrite("Loop2"&@CRLF) ; And at the same time I sleaping 100 Milliseconds
EndFunc   ;==>Example


Func Exit1()
    Exit
EndFunc

I do not know if it is real multithread but I think it does not really matter because it does what multithread does

according to how it works..

 

It is still very Good thing to know..

 

But anyway it's still interesting to me if this is real multithread.

It's a way to run more then one loop at the same time with no effect from Sleap outside the loop.

Each loop is not affected by Sleap() outside the loop and this is another major advantage ..

 

But these loops are written In a different way (read more >here)

Are there any disadvantages In this method?

Edited September 7, 2014 by Guest

[JohnOne]

It is certainly not multi threading, and no loops are running at the same time.

Poor trolling.

3/10

[Jos]

Your example has nothing to do with mulitythreading.

The regular process is simply interupted for the defined adlib funcs and will continue when they are done.

Jos

[Guest]

It is certainly not multi threading, and no loops are running at the same time.

I was just asking a question ..

i know that these are not loops but they work like loops so i call them loops.

loop is some code that run again and again every period of time.

If you judge it by the result,

in this code:

While 1
    ConsoleWrite("code" & @CRLF)
    Sleep(1000) ; I am sleaping 1000 Milliseconds!!
WEnd

and in this code:

AdlibRegister("Loop",1000)
Func Loop()
    ConsoleWrite("code" & @CRLF)
EndFunc  

While 1
    Sleep(10)
WEnd

the result is code that run again and again every 1 Second.

So If I look at the result then i can call it a loop..

And I did not say that it is multi threading.. I'm just asking if this is really multi threading

Edited September 7, 2014 by Guest

[Jos]

I was just asking a question ..

And I did not say that it is multi threading.. I'm just asking if this is really multi threading

And the answer is no.

[BrewManNH]

It's not multithreaded, it's not even pretend multithreading. It's just pausing one function to run another, then going back to the first function.

[Guest]

It's not multithreaded, it's not even pretend multithreading. It's just pausing one function to run another, then going back to the first function.

 

Ok, I am not surprised that this is the answer.

 

 

I think that this kind of loops is much better than Regular loop.

I see a lot of potential in this type of loop.

I know you may not call it a loop and you may have good reasons.

But from a human perspective, it seems to me like a loop

.

Edited September 7, 2014 by Guest

[Jos]

Call it what you like, but both of your example code snippets serve a different purpose.

Jos

Edited September 7, 2014 by Jos

[JohnOne]

My super loop is the boss of your loop.

Loop()

Func Loop()
    Sleep(500)
    ConsoleWrite("Tra la" & @LF)
    Poop()
EndFunc

Func Poop()
    Sleep(500)
    ConsoleWrite("di da" & @LF)
    Loop()
EndFunc

[guinness]

Then the user will be asking what does stack overflow mean?

[JohnOne]

The user of that deserves stack overflow.

[Guest]

 

My super loop is the boss of your loop.

Loop()

Func Loop()
    Sleep(500)
    ConsoleWrite("Tra la" & @LF)
    Poop()
EndFunc

Func Poop()
    Sleep(500)
    ConsoleWrite("di da" & @LF)
    Loop()
EndFunc

lol, you made a loop with two functions.

It's an interesting subject.

It does not "loop" and it is "overflow" ?

 

If so what are the differences between "loop" and "overflow"?  There is no difference right?

it looks the same thing

 

Maybe I'm asking stupid questions..

Edited September 8, 2014 by Guest

[guinness]

Maybe try it before posting.

[JohnOne]

 

lol, you made a loop with two functions.

It's an interesting subject.

It does not "loop" and it is "overflow" ?

 

If so what are the differences between "loop" and "overflow"?  There is no difference right?

it looks the same thing

 

Maybe I'm asking stupid questions..

 

Guinness is saying unrestricted recursion will eventually cause stack overflow.

[Guest]

Guinness is saying unrestricted recursion will eventually cause stack overflow.

Oh, I see.

In fact I've seen in the past this form of coding. But I did not think that it will cause a fatal error in stress case...

If you would post this example:

Loop()

Func Loop()
    Poop()
EndFunc

Func Poop()
    Loop()
EndFunc

then i know what you're talking about more earlier

 

I have an important question(this is important for me) and it is also nice game

#include <ButtonConstants.au3>
#include <GUIConstantsEx.au3>
#include <WindowsConstants.au3>


Test()

Func Test()
    Local $Form1 , $Button1 , $nMsg
    #Region ### START Koda GUI section ### Form=
    $Form1 = GUICreate("Game Click", 250, 85, 233, 150)
    $Button1 = GUICtrlCreateButton("Click", 72, 24, 97, 41)
    GUISetState(@SW_SHOW)
    #EndRegion ### END Koda GUI section ###

    While 1
        $nMsg = GUIGetMsg()
        Switch $nMsg
            Case $GUI_EVENT_CLOSE
                Exit
            Case $Button1
                ExitLoop
        EndSwitch
    WEnd
    GUIDelete($Form1)
    Test()
EndFunc

How many times you need to click on the "click" until  you see the error:

Recursion level has been exceeded - AutoIt will quit to prevent stack overflow.:

EDIT:

I tried many times to press the button "Click" and i didn't got the error..

So that bug that i found is almost unreachable

Edited September 8, 2014 by Guest

[JohnOne]

Recursion level is explained in the helpfile somewhere. If I recall AutoIt handles it internally so I'm not so sure that this kind of recursion can cause stack overflow in AutoIt really.

Edited September 8, 2014 by JohnOne

[Guest]

Recursion level is explained in the helpfile somewhere. If I recall AutoIt handles it internally so I'm not so sure that this kind of recursion can cause stack overflow in AutoIt really.

Actually yes If you click on the button more then 3899 times.

I cheated the game..

I tested it with the codes:

Global $a = 0
Test()


Func Test()
    $a += 1
    ConsoleWrite($a & @CRLF)
    Test()
EndFunc

and

Func Test()
    $a += 1
    Local $Form1 , $Button1 , $nMsg
    #Region ### START Koda GUI section ### Form=
    $Form1 = GUICreate("Game Click", 250, 85, 233, 150)
    $Button1 = GUICtrlCreateButton("Click", 72, 24, 97, 41)
;~     GUISetState(@SW_SHOW)
    #EndRegion ### END Koda GUI section ###

    GUIDelete($Form1)
    ConsoleWrite($a & @CRLF)
    Test()
EndFunc

In both cases I get the same number

Edited September 8, 2014 by Guest

[Gianni]

look here:

Maximum number of times the Call() function can recurse to itself.:      3900 limit for x64 and 1900 limit for x86

[guinness]

look here:

 

Maximum number of times the Call() function can recurse to itself.:      3900 limit for x64 and 1900 limit for x86

That value changes from time to time.

[JohnOne]

And Call() or Execute() is not used here.