3 ms·
"One of the strengths that Java has over Lisp is that it's statically typed." Common Lisp has optional static typing. Unlike Java, you have the choice, dependi
by bachmeier 12y ago
"One of the strengths that Java has over Lisp is that it's statically typed."
Common Lisp has optional static typing. Unlike Java, you have the choice, depending on what you're doing.
- xenophonf 12y agoHere's a good discussion of static typing in Common Lisp: http://www.lispforum.com/viewtopic.php?f=2&t=191 http://www.lispforum.com/viewtopic.php?f=2&t=191 TL;DR is that many CL implementations will check types at compile time, but for appropriate speed and safety settings, they will also generate code that checks types at runtime, too.
- lisper 12y ago> Common Lisp has optional static typing That depends on what you mean. CL declarations are promises to the compiler. They permit the compiler to make optimizations but does not require it to signal compile-time errors. Specific implementations may give you compile-time errors, but in general you can't count on it the way you can in Java.