> On 06.05.20 18:42, John Duncan wrote: > Picolisp is interpreted. Even the llvm version is just creating an > interpreter. There is no JIT. Exactly!
Guido, you should really stop talking about things you so obviously have no understanding of. There is NO COMPILING when executing program written in PicoLisp. Nowhere. > Since the AST (Abstract Syntax Tree) in any Lisp is changing all the > time, the JIT engine *has to* post-jit continuously to keep up the > full execution speed. > That's what will give pil21 a real performance boost over over any > 'static compiled' implementation. Wrong. PicoLisp is having Fexpr's (in opposition to Macros), and Fexpr's can be impossible to compile at all. pil21 is not about performance, but compatibility. pil21 is expected to even run a bit slower then the current amd64 ASM implementation. The core principles of PicoLisp are simplicity and practicality - raw speed is not the goal, optimizing developer time is. - beneroth -- UNSUBSCRIBE: mailto:picolisp@software-lab.de?subject=Unsubscribe
