Dennis Clark wrote: > Ouch. My experience with LISP was totally interpreted, not byte-code > compiled like Java. Times and compilers change! That must have been some time ago for "totally" interpreted Lisp. I'm only aware of one Lisp that compiles to to Java-like byte code -- that's clisp. All the other Lisp implementations compile to native machine code. Lisp does permit one to have interpreted as well as compiled code. But as a matter of procedure, it's just as easy to compile and load code than use interpreted, non-compiled code. Lastly, Lisp does have some fanciness in that you can direct things to be done at different times: read-time, macroexpansion-time, compile-time, load-time, and execute-time. Kevin
Message
Re: [AVR-Chat] New version of avrcalc uploaded
2008-01-14 by Kevin Rosenberg