On Tue, Feb 18, 2014 at 11:38 PM, Devin Walters dev...@gmail.com wrote:
You need to use the lein plugin for no.disassemble, not the dependency.
The README explains how.
Thanks - now I can see disassembled code - quit neat. I misread do not use
this way as a following as opposed to above
The OP almost certainly intended CLISP to mean Common Lisp.
I recall it now - it was Allegro CL which somebody demoed to me almost ten
years ago. I wish I started learning Lisp yet cannot believe that Clojure I
am learning now (and Scala I am actively using) did not exist back then.
--
You
Hi,
There are many performance benchmarks showing that compiled CLISP is almost
as fast as C++ or Clojure as Java.
Being a dynamically typed language though, I wonder how it is possible. Is
it because the compiler is able to sort out actually used types and
assemble appropriate byte code or the
For Clojure at least, it is a combination of things, including:
- The quality of the optimisations that the JVM itself does during JIT
compilation. Virtual method calls for example are crazily fast.
- The JVM garbage collector - which is seriously good.
- The ability to use type hints and
It really depends on the benchmark and the programmer, and sometimes on the
computer. And on what a person chooses to report. Here are some
benchmarks, probably only representative of very special cases, that show
Java beating Clojure in many cases, Java and SBCL both beating each other
in
Clojure IMO is not truly dynamic, at least not to the extent of
Python/Ruby. I like to refer to Clojure as a dynamic enough language.
For example, once defined, types cannot be modified by adding new members
(deftype that is). If you want to add a new field to a deftype in Clojure,
you have to
Thanks for the insight and link to http://benchmarksgame.alioth.debian.org.
WRT dynamically typed languages, I have some 5 years experience with Python
circa 2.4ish timeframe. I remember that a practical raw speed was not that
bad, but still was in average like 10 times slower from C++. Good
The OP almost certainly intended CLISP to mean Common Lisp. While the
CLISP implementation of Common Lisp is a decent platform (Conrad Barski
features it in his book _Land of Lisp_, for example), it is not the fastest
implementation. Their documentation acknowledges as much:
You need to use the lein plugin for no.disassemble, not the dependency. The
README explains how.
Cheers,
'(Devin Walters)
On Feb 18, 2014, at 23:16, Andy C andy.coolw...@gmail.com wrote:
Thanks for the insight and link to http://benchmarksgame.alioth.debian.org .
WRT dynamically typed
