recursivity - (Moved)

[caramen]

Is it normal that AutoIt doesn't have the same recursivity behavior in win 7 and W10 ?

[water]

What do you mean by "recursivity behavior"?
How did you notice that it is different between W7 and W1ß?

Edited December 9, 2020 by water
Fixed typo

[Nine]

Do you have a proof of that ?  Sincerely, I use quite a bit of recursive algorithms and I never seen any difference Win7 and Win10.

Edited December 9, 2020 by Nine

[water]

Check the AutoIt limits and you will see that recurse limits depend on the bitness.

[caramen]

8 hours ago, Nine said:

Do you have a proof of that ?

It is a funny story...If you read my recent helps threads, and I think you did, you already know.

But I'll say all again. I made a tool 10 years ago for one of my customer. One of the customer after I left them thief my sources. And he worked on my tool and changed everything. This should not happen because in France my windows account is my property. It is my data and it remains for 80 years. 

They called me 10 years after to work on automatization of multiple processes. And they told me, bro the tool is buggy on Windows 10 and it was not on win7 could you please check that ?

I what was my surprise when I checked... They modified all my copyrights ... nvm. 

I checked the sources. From my experience recusivity was usable without problems. Without memory saturation etcetera.... But the tool was old And 10 years before I was not coding like now. So the code was ugly but it has a reliability of 100%.

So my mission on this was to debug 4000 lines code from my hold methods. Yesterday. I was gonna fall asleep. And I thought about the recursivity of this script and I removed it. the script is now reliable 100% back even on win10.

 

Here his how it was:

The recursive example : 

Menu()

Func Menu ()
    While 1
        Sleep ( $Pause3 )
            If _IsPressed(""&$hShordCutKey, $dll) Then
                 _CreationMenu()
            EndIf
    WEnd
EndFunc

Func _CreationMenu()
   While 1
      Switch GUIGetMsg()
         Case $GUI_EVENT_CLOSE
            ExitLoop
         Case $Close
            FuncClose ()
         Case $MasqueSymptome   ;~ Insérer un masque Symptôme
            Func1000 ()
      EndSwitch
    Wend
EndFunc     

Func FuncClose ()
   _CleanAndWait ()
   Menu ()
   ConsoleWrite ("Test"&@CRLF) 
EndFunc

So just above the example is recursive because the menu () func is calling herself. If the $Close is catched by guigetmsg 

Without recursivity ;

While 1

    Menu()

WEnd

Func Menu ()
    _OnDesactiveLaSecu ()
    _OnSecureLesTouches ()
    Sleep(500)
    While 1
        Sleep ( $Pause3 )
            If _IsPressed(""&$hShordCutKey, $dll) Then
                 _CreationMenu()
            EndIf
    WEnd
EndFunc

Func _CreationMenu()
    While 1
      Switch GUIGetMsg()
         Case $GUI_EVENT_CLOSE
            ExitLoop
         Case $Close
            FuncClose ()
            ExitLoop
      EndSwitch
    Wend
EndFunc

Func FuncClose () 
   _CleanAndWait ()
   ConsoleWrite ("test"&@CRLF)
EndFunc

 

 

WIn 7 behavior : 

The script is doing the create menu function without problem. 

Win 10 

The script is finishing the first Menu () function what ever happen before. The recursivity make the script buggy. 

Edited December 10, 2020 by caramen

[Jos]

2 hours ago, caramen said:

The recursive example : 

This is simply bad coding where you never properly end but simply keep on going deeper and deeper in recursion. It will eventually fail in all OSes... just a matter of time and available stacksize..

Jos

[Jos]

Moved to the appropriate forum.

Moderation Team

[caramen]

5 hours ago, Jos said:

This is simply bad coding where you never properly end but simply keep on going deeper and deeper in recursion. It will eventually fail in all OSes... just a matter of time and available stacksize..

Jos

I agree with that.

[JockoDundee]

13 hours ago, caramen said:

They called me 10 years after to work on automatization of multiple processes. And they told me, bro the tool is buggy on Windows 10 and it was not on win7 could you please check that ?

Sounds like the customer blew their stack

[rudi]

Not directly related to your example, I'd like to mention that the NTFS file system can offer problems by placing (defective) reparse points.

 

If recursive search loops come across such a reparse point, pointing to it's own parent directory, the logic will "loop-infinitely-into-death".

I mostly have seen this for "ProgramData"  = "Anwendungsdaten" in German Windows installations, both, Windows 7 and Windows 10. Looks like this:

 

This can be resolved using FSUTIL.EXE 

 

C:\Users\All Users>cd "Application Data"
 C:\Users\All Users\Application Data>cd "Application Data"
 C:\Users\All Users\Application Data\Application Data>fsutil hardlink list .
\ProgramData\Application Data
 C:\Users\All Users\Application Data\Application Data>cd ..
 C:\Users\All Users\Application Data>fsutil reparsepoint delete "C:\Users\All Users\Application Data\Application Data"
 C:\Users\All Users\Application Data>cd "Application Data"
system cannot find path specified (German: "Das System kann den angegebenen Pfad nicht finden.")
 C:\Users\All Users\Application Data>