Running external programs

[stefano]

In most applications it's required to run an external program and wait for its termination before proceeding.
The JustBasic "run" statement, instead, does not seem to have a way for waiting.
What's the suggested way to achieve "run a program and wait until completed" ?

[Rod]

This requires API work which is out of scope for Just BASIC. ShellExecute is the topic to research on Liberty BASIC forums.

[cundo]

Sept 7, 2018 10:59:36 GMT stefano said:

In most applications it's required to run an external program and wait for its termination before proceeding.
The JustBasic "run" statement, instead, does not seem to have a way for waiting.
What's the suggested way to achieve "run a program and wait until completed" ?

Hello Stefano, is that other "external program" written in JB?

[stefano]

Sept 8, 2018 17:17:52 GMT cundo said:

Sept 7, 2018 10:59:36 GMT stefano said:

In most applications it's required to run an external program and wait for its termination before proceeding.
The JustBasic "run" statement, instead, does not seem to have a way for waiting.
What's the suggested way to achieve "run a program and wait until completed" ?

Hello Stefano, is that other "external program" written in JB?

I would need to run any external executable Windows program. What's missing is just a way to wait for synchronous termination
of the spawned process. I suppose it's already possible with Liberty Basic since you can call Win32 API DLL functions.

Anyway, a solution could be (in some cases) to stay in a loop until some file has been created by the spawned program.

p.s. would it be easier if the "external program" is written in JB as you mentioned ?

[cundo]

See this

Synchronous vs asynchronous
As was stated, "The JB program will continue to run". More precisely, then running EXE program, (or BAT file), JB continue to line following RUN statement instantly, without waiting for RUN'd program to finish. (actually JB has no means to tell if it finished). This is, EXE program runs asynchronously.
If you run another JB program via runtime
run "jbrun101.exe myProg.tk
, your code will continue instantly along with running myProg.tkn.
BUT
if you run TKN without mentioning runtime engine
run "myProg.tkn"
, your code will *HALT* and *WAIT* till code in myProg.tkn finishes.
This is, TKN program runs synchronously.
Probably this way, it uses same engine as your main (caller) program.
this is not documented - experiment first.

This comes from the Wiki, tsh added it

[stefano]

Sept 11, 2018 22:56:28 GMT cundo said:

See this

Synchronous vs asynchronous
As was stated, "The JB program will continue to run". More precisely, then running EXE program, (or BAT file), JB continue to line following RUN statement instantly, without waiting for RUN'd program to finish. (actually JB has no means to tell if it finished). This is, EXE program runs asynchronously.
If you run another JB program via runtime
run "jbrun101.exe myProg.tk
, your code will continue instantly along with running myProg.tkn.
BUT
if you run TKN without mentioning runtime engine
run "myProg.tkn"
, your code will *HALT* and *WAIT* till code in myProg.tkn finishes.
This is, TKN program runs synchronously.
Probably this way, it uses same engine as your main (caller) program.
this is not documented - experiment first.

This comes from the Wiki, tsh added it

[stefano]

Thanks. Good to know, even if it seems not an official feature.

[zzz000abc]

Sept 12, 2018 7:54:58 GMT stefano said:

Sept 11, 2018 22:56:28 GMT cundo said:

See this This comes from the Wiki, tsh added it

good question better explanation thank you all