Take a look: https://blog.area9lyceum.com/area9-open-sources-flow-program...
It means compiler caches results of module compilation and reloads them if module didn't change. Hot code reloading is not supported.
We have some support for concurrency in Java and JavaScript backends, see lib/sys/concurrent.flow.
The call chain is: - you run flowcpp and feed it with .flow file; - flowcpp see that it is source file and calls compiler - compiler produces .bytecode file - flowcpp executes .bytecode file and runs file you called.…
You need to rebuild QtByteRunner. Cd to platforms/qt/. There is a readme there for full explanation, but in short: - clone asmjit (https://github.com/area9innovation/asmjit.git) into platforms/common/cpp folder first…
Take a look: https://blog.area9lyceum.com/area9-open-sources-flow-program...
It means compiler caches results of module compilation and reloads them if module didn't change. Hot code reloading is not supported.
We have some support for concurrency in Java and JavaScript backends, see lib/sys/concurrent.flow.
The call chain is: - you run flowcpp and feed it with .flow file; - flowcpp see that it is source file and calls compiler - compiler produces .bytecode file - flowcpp executes .bytecode file and runs file you called.…
You need to rebuild QtByteRunner. Cd to platforms/qt/. There is a readme there for full explanation, but in short: - clone asmjit (https://github.com/area9innovation/asmjit.git) into platforms/common/cpp folder first…