It is possible to create a binary executable with most scripting languages by building a binary that includes a full copy of the script interpreter and the script in source form. It is typically referred to as encapping a script. I'm sure this is the process with LiveCode.
The technique is even used to produce a binary executable of Java programs though in those cases the Java byte code is encapped with a JVM. This technique is used for the JEdit text editor. Peter On 8 Feb 2013, at 20:20, Mark Smith wrote: > Monte Goulding wrote >> The engine is a mash up of c++ and platform obj-c on iOS and java on >> android. Our scripts are compiled as they are loaded into memory not at >> runtime. > > Interesting. I've never heard of that model before. A load-time compiler? So > it neither distributes compiled binaries (machine code) or p-code > (pre-compiled binaries for execution by a runtime interpreter), but rather > source code that gets compiled and executed at (technically runtime but not > in the same sense as an interpreter, more in the sense of a compiler??). > Gosh, I don't even think I can coherently describe that :-) > > This does represent an interesting hybrid model. Thanks Monte > > -- Mark > > > > > -- > View this message in context: > http://runtime-revolution.278305.n4.nabble.com/what-is-LCs-output-for-different-platforms-tp4660332p4660335.html > Sent from the Revolution - User mailing list archive at Nabble.com. > > _______________________________________________ > use-livecode mailing list > use-livecode@lists.runrev.com > Please visit this url to subscribe, unsubscribe and manage your subscription > preferences: > http://lists.runrev.com/mailman/listinfo/use-livecode _______________________________________________ use-livecode mailing list use-livecode@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-livecode
