Neither list processing nor run-time binding is very special anymore. See Python, for example. And think I'd rather work in Python, although I haven't yet. It seems to me to be a little less error-prone in a couple of respects: grouping of statements is quite visible, while in LISP all grouping is controlled just by parentheses, and in Python you have the option whether or not to specify the types of objects, while in LISP you have no choice but to hope that it gets it right when it looks at the data at runtime.
You might like to check out Axel on www.spherum.com. It runs under Lisp, includes
pattern-directed list handling, static type checking on demand and uses an approach to types
more advanced than just about any on offer.
Slashdot Mirror
Neither list processing nor run-time binding is very special anymore. See Python, for example. And think I'd rather work in Python, although I haven't yet. It seems to me to be a little less error-prone in a couple of respects: grouping of statements is quite visible, while in LISP all grouping is controlled just by parentheses, and in Python you have the option whether or not to specify the types of objects, while in LISP you have no choice but to hope that it gets it right when it looks at the data at runtime.
You might like to check out Axel on www.spherum.com. It runs under Lisp, includes pattern-directed list handling, static type checking on demand and uses an approach to types more advanced than just about any on offer.