Different Behavior, Script vs. Compiled/Linked

[semperos]

I'm glad I'm not going mad, either :-)



The only reason I tried it was that I was trying out a few new Lisps (Clojure is my primary language) and was interested in platform executable compilation, as Clojure only compiles to Java artifacts that require a bit more setup to be used as scripts.



Thanks for all the help!

[cormullion]

I suspect there's little speed difference for shorter scripts between linked executables and plain scripts. Also, it's much easier to update and modify scripts when they're independent of the newLISP binary. (There's also the slight risk of losing the original source... :)  



I can see that the feature of bundling everything together is useful, though.

[Lutz]

Again: link.lsp doesn't compile anything, it just takes the source script, encrypts it and appends it to the end of a newLISP executable. So speed wise there is no difference in execution of the script, linked or not.

[semperos]

Yep, understood on how link.lsp works. newLISP is plenty fast; my only goal was to create self-contained and portable utilities to share between identical machines (at my work).

[Lutz]

Not sure how your work machines are configured, but if they are OSX/UNIX machines, all with user writable $HOME/bin directories,  you could write a small shell script copying the newlisp executable and script over the office network. This way you only need to distribute one file initially.