Liberty BASIC v5.0 compiler and runtime mechanism
Feb 25, 2019 16:24:28 GMT -5
cundo and donnybowers like this
Post by Carl Gundel on Feb 25, 2019 16:24:28 GMT -5
Since inquiring minds want to know...
Liberty BASIC v5.0 still compiles into an intermediate execution model that executes on top of the Smalltalk virtual machine. However the approach that is used is completely different from the legacy Liberty BASIC approach.
There is a two pass compiler, like in previous versions of LB. The execution model is much more structured and modular, and more flexible. An end result of this better performance. Alpha testers will notice some things are faster and some slower, but in the end almost everything should be faster.
The runtime compile that I mentioned in another thread is related to dynamically loading BASIC code into a running BASIC program. The discussed LIBRARY keyword could be made to load and compile statically or dynamically as needed.
The way that runtime deployment will happen is that an *.im file will be generated with the compiled objects in it. This will be more secure than the current runtime system. There will be no tokens at all. This application file will be executed by the VM. The way this will be approached will be different depending on the OS. For Windows the VM will be named myapp.exe and the application image will be myapp.im. Running the myapp.exe will automatically run the myapp.im. On the Mac you can simply create a standard Mac application folder/object and stick all the required files inside which makes a double clickable app. I'm still weighing options for the Linux/Raspian deployment technique.
Does this help?
Liberty BASIC v5.0 still compiles into an intermediate execution model that executes on top of the Smalltalk virtual machine. However the approach that is used is completely different from the legacy Liberty BASIC approach.
There is a two pass compiler, like in previous versions of LB. The execution model is much more structured and modular, and more flexible. An end result of this better performance. Alpha testers will notice some things are faster and some slower, but in the end almost everything should be faster.
The runtime compile that I mentioned in another thread is related to dynamically loading BASIC code into a running BASIC program. The discussed LIBRARY keyword could be made to load and compile statically or dynamically as needed.
The way that runtime deployment will happen is that an *.im file will be generated with the compiled objects in it. This will be more secure than the current runtime system. There will be no tokens at all. This application file will be executed by the VM. The way this will be approached will be different depending on the OS. For Windows the VM will be named myapp.exe and the application image will be myapp.im. Running the myapp.exe will automatically run the myapp.im. On the Mac you can simply create a standard Mac application folder/object and stick all the required files inside which makes a double clickable app. I'm still weighing options for the Linux/Raspian deployment technique.
Does this help?
