my background is windows desktop and in general it is very procedural in that each line is executed in the order it is presented.
The flowing sub would execute every line myFakeProc1 before proceeding to MyFakeProc2 (* unless of course I run each procedure in its own thread, which i have to go out of my way to do)
my impression of this language is that myFakeProc2 is started immediately after myFakeProc1 while myFakeProc1 may in fact still be executing
Hence we use wait for to ensure the statements that follow it are not executed until the wait for procedure is completed
If this is case, for me it feels like it uses threading inherently, so I'm wondering why there is also a threading library?
The flowing sub would execute every line myFakeProc1 before proceeding to MyFakeProc2 (* unless of course I run each procedure in its own thread, which i have to go out of my way to do)
B4X:
Private Sub DoSomething()
myFakeProc1
myFakeProc2
End Sub
my impression of this language is that myFakeProc2 is started immediately after myFakeProc1 while myFakeProc1 may in fact still be executing
Hence we use wait for to ensure the statements that follow it are not executed until the wait for procedure is completed
If this is case, for me it feels like it uses threading inherently, so I'm wondering why there is also a threading library?