3 ms·
So what paradigm would you suggest? A combination of imperative with functional where it's better suited? Or is Lisp best programmed with an entirely new approa
by proaralyst 10y ago
So what paradigm would you suggest? A combination of imperative with functional where it's better suited? Or is Lisp best programmed with an entirely new approach?
- pavelludiq 10y agoDepends on your problem, experience level, and the context of your overall architecture, team or a million other factors. Apply thought liberally :)
- shakna 10y agoLisp is a family of languages. CL doesn't define all Lisps. The two big families tend to be Common Lisp and Scheme. * Clojure - Immutable, functional, has pattern matching. * Common Lisp - Mostly just multiparadigm, with a leaning towards Object Oriented. * Scheme - More functional than Common Lisp, less Object-Oriented. (Though Guile tends to have an OO leaning, through its extensions.) * Racket - Has a mix of lazy, static typed and other sublanguages. * Picolisp also deserves an honorable mention. It is somewhere between Common Lisp and Scheme, with some clever language features of its own. It's mostly functional, with decent C/Java FFI and a Datalog-like library for OO.