Although Clojure still has a `cons` it has been replaced by `seq` as the fundamental abstraction. Clojure takes advantage of being fully managed code and in a sense is as much a Lisp as C# is a C [if we were inclined to think of C as a genre, else Algol?].
It seems this, combined with a formally incorporating a DSL of the kind a experienced Lisper (such as Hickey) might create for writing programs gives Clojure it's syntax: e.g. [x y] is syntactically like a quoted list and writing a macro is the sort of thing hubris drives lazy impatient Lispers to do. In special forms [x y] is like a different more complex macro, but again the sort of thing people would write for themselves. In other Lisps the ad hoc nature of such macros however makes other people's code notoriously hard to follow.
Yeah, cons is like malloc, except that the object it creates is automatically memory managed / garbage collected. There is no corresponding "free" call. Actually, that means cons is not like malloc.
Clojure takes advantage of being fully managed code
Do you realize that Lisp uses automatic memory management (just like the JVM or CLR)?
Why are there no Fortran machines or Algol Machines or C machines?
The `cons` cell is a raw memory structure, just one step removed from assembly and originally accessed directly in machine code with `car` and `cdr`. It's associated symbol is literally a pointer directly to a memory location. It's so close to assembly language that thirty years ago implementing it directly in hardware was considered practical.
It's associated symbol is literally a pointer directly to a memory location
A cons is not "raw memory"; it is a typed data structure, and in Common Lisp it is even considered an OOP object of the cons class. It is equivalent to having a data structure called "pair" that can hold two things.
All memory-allocated data structures ultimately have an address of some kind, so this whole discussion about pointers is utterly meaningless. For that matter, arrays, strings, and basically every known memory data structure is "raw" too. After all, they have an address.
The fact that cons/car/cdr can be implemented cheaply in hardware stems from the fixed and small size of cons. That doesn't make it somehow inferior.
By the way, the Java stuff is implemented in hardware too, does that make Java inferior? http://en.wikipedia.org/wiki/Java_processor
> Although Clojure still has a `cons` it has been replaced by `seq` as the fundamental abstraction.
Common Lisp has lists and sequences as abstractions. But it does not take away the low-level operations.
I'm not making a case that Clojure is better than other Lisps - getting rid of `cons` and relying on the JVM has makes typing more critical in an environment that retains a degree of type opacity typical of dynamic type systems.
See SERIES in Common Lisp. http://series.sourceforge.net
> At a higher level the abstraction facilitates differentiating a breadth first search tree from a depth first search tree as types of data structures
Typically used as CLOS libraries in Common Lisp.
> getting rid of `cons`
That's caused because Clojure is implemented in something else and doesn't go very deep.
Common Lisp goes deeper because it is it's own implementation language. Much of the implementations are written in Common Lisp itself (compiler, parts of the runtime, ...). On something like the MIT Lisp Machine even the garbage collector was written in Lisp.
Lisp is reflective building material + machineries + some pre-build stuff.
Clojure is more like pre-built stuff on top of some other infrastructure.
All that said, what Clojure shares with Common Lisp, is that practical programming issues come first and that theology comes last - in the end all questions of doctrine can be resolved in the mathematics of the lambda calculus.
Clojure and Common Lisp express the same attitude toward programming and programmers. Their attitude toward academic computer science is perhaps a bit different, largely for reasons of history: Lisp has one, Clojure doesn't.
> Moreover, the last standardization was grounded in the previous effort and that was before GNU and when dedicated hardware looked like the future.
Hmm, Common Lisp was developed to run efficiently on stock hardware from day one. Motorola 68k, Intel 86, then SPARC, POWER, MIPS, ...
> Clojure and Common Lisp express the same attitude toward programming and programmers.
They don't.
Common Lisp was developed as a standard Lisp language for application development (in domains like expert systems, cad systems, etc.) which favors giving the programmer maximum freedom and makes little assumption on what it is running.
Example: Common Lisp comes with minimal expression syntax and an extension mechanism.
Clojure was originally developed to bring a Lisp to the JVM, which integrates with Java, reuses parts of Java and favors things like functional or concurrent programming.
Example: Clojure comes with more complex expression syntax and no extension mechanism.
I stated that Common Lisp was developed before the commercial internet & args.
symbolics.com, Lisp Machine manufacturer, first ever .com domain. In 1985.
bbn.com, Lisp Machine developer, second .com domain in 1985.
Thinking Machines, Parallel AI Machine for Lisp, third .com domain in 1985
MCC, had hundreds of Lisp Machines, fourth .com domain in 1985
DEC, co-sponsor of CL, fifth .com domain in 1985
Xerox, Lisp Machine developer, seventh .com domain in 1986
...
I'd say all the companies who participated in the CL development from 1981-1994 were commercial entities on the Internet. All of them offered a variety of network services in their operating systems: mail, chat, terminal, X11, file sharing, remote printing, remote booting, name server, ...
http://en.wikipedia.org/wiki/List_of_the_oldest_currently_re...
All were having networked machines and networked operating systems.
However, I am in no way implying that the creation of the .com TLD is the resolution of the phrase "commercial internet" in ordinary language & args.
You wrote:
> I'm not advancing a moral argument. I'm advancing an historical one. It's an amoral fact that Common Lisp was standardized more than twenty years ago
It was standardized 1994 with the ANSI CL standard. Exactly 20 years ago.
> - before the commercial internet,
Commercial ISPs started around 1989.
> wide availability of systems suitable for distributed computing,
Distributed computing was available earlier.
> and even before it was clear that GUI's would win the war.
Lisp supported GUIs much earlier. The Common Lisp standards group had even a subgroup for this topic.
Anyway it's not clear what this all means, when CL was developed. Scheme, Objective C, C, C++, Smalltalk, were all developed before Common Lisp. What follows from that?
>Clojure takes advantage of being fully managed code
>writing a macro is the sort of thing hubris drives lazy impatient Lispers to do
The ignorance of Clojure programmers is really incredible.
(foo '(1 2 3)) simply becomes (foo [1 2 3])
Common Lisp:
A vector:
CL-USER 34 > #(1 2 3)
#(1 2 3)
A string: CL-USER 35 > "1 2 3"
"1 2 3"
A structure: CL-USER 36 > #S(FOO :A 1 :B 2 :C 3)
#S(FOO :A 1 :B 2 :C 3) lambda (x)(+ x 1)
defun f (x)(+ x 1)
Syntactically `(x)` looks like it should be evaluated, but isn't because there are special rules for special forms, and each special form can have it's own rules: let ((x 7)(y 3))
(+ x y)
is a whole `nother set of syntactical rules which are even more in conflict with normal rules of evaluation.Scheme, keeps the let and uses a syntax for `define` that mimics the function call rather than the lambda.
define (f x) (+ x 1)
f 1
In Clojure the use of a vector for `defn` arguments follows it's formal lambda form like Common Lisp and is very much consistent with Clojure's rules for evaluation. fn [x] (+ x 1)
defn f [x] (+ x 1)
Likewise Clojure's `let` syntax does not require wetware parsing to recognize what gets evaluated and what doesn't. let [x 1
y 3]
(+ x y)
What I am appreciating about Clojure as a language is that it prunes some historic artifacts from the Lisp family tree. Raw memory allocation with `cons` made sense when human memory could retain more facts than a computer's fast memory. This meant it was easy to think of useful programs too big to fit in memory. That's distinctly harder today where doubling fast memory is less than $300 for the vast majority of computers.Lisp was developed as a direct improvement over assembly. Clojure was developed as a direct improvement over Java over C++ over C over assembly. It's a rethinking of what a Lisp needs (when backwards compatibility is ignored). It's an interesting design.
Using array syntax for arglists is just arbitrary. Clojure is inconsistent anyway.
(defmacro and
([] true)
([x] x)
([x & rest]
`(let [and# ~x]
(if and# (and ~@rest) and#))))
Can you explain why this has parentheses: ([x] x) ? Is that meant to be evaluated?> Likewise Clojure's `let` syntax does not require wetware parsing to recognize what gets evaluated and what doesn't.
let [x 1
y 3]
(+ x y)
This is all inconsistent. A vector [x 1 y 3] is evaluated. But in LET 1 and 3 are evaluated. x and y not.> What I am appreciating about Clojure as a language is that it prunes some historic artifacts from the Lisp family tree.
Clojure adds more artifacts than it removes.
> Lisp was developed as a direct improvement over assembly.
Lisp was developed for symbolic computation with recursive functions in the domain of list processing. It has nothing to do with assembler.
> It's a rethinking of what a Lisp needs (when backwards compatibility is ignored).
It's a rethinking what a Java programmer might want as the next step. As Lisp not so much.
> It's an interesting design.
That's true.
"Can you explain why this has parentheses: ([x] x) ?"
For the same reason "((= a 2) (setq a 3))" has parentheses in:
(cond ((= a 1) (setq a 2))
((= a 2) (setq a 3)) (cond (= a 1) (setq a 2)
(= a 2) (setq a 3))
Seems like it could serve exactly the same purpose?The initial thought would be for structure: cond takes any number of arguments, each made up of a conditional -> expression pair. Your suggestion, which is exactly my initial belief before it burned me back in the day, would make cond take an alternating list of conditions and expressions; clearly that's not nearly as beautiful.
The structural argument is wrong, though, and your suggestion doesn't work at all. For what must have seemed practical reasons at the time, the expression side is an implicit PROGN, so you can do "((= a 2) (setq a 3) (setq b (potato)))".[1]
Common Lisp has some wacky syntax. Large chunks of which are historically (hystorically?) path-dependent. Anyone who tells you otherwise risks calling up the viscous LOOP troll.
In Clojure, the defmacro thingy looks like it takes muliple expressions after the params in the body there, so it needs ()'s around the individual cases.
[1] http://www.lispworks.com/documentation/lw60/CLHS/Body/m_cond...
The reason you have those parenthesis on defmacro is that defmacro shares syntax with defn and fn for function declaration; in turn, these allow for multiple side-effecting statements in a function. For example:
(defn my-function [args]
(prn "Hello, world!") ; do something with side effects...
args) ; then return a value
This works fine in the single-dispatch case, but when you're declaring a function that takes multiple arities (with a different implementation dispatched for each), there's no way to tell where each arity ends and the next begins - after all, something like [args] is just data and could easily be a valid expression. The parenthesis are then needed to disambiguate where one arity ends and the next begins: (defn greet
([] (println "Hello, there!")
(swap! greeting-count inc)
:greeted)
([name] (println "Hello, " name)
(swap! greeting-count inc)
:greeted))
This is a space where clojure seems a bit inconsistent - let, fn, loop, and try all allow multiple expressions, while cond and if don't (but you can get it back using the (do) special form). This however does have some logic to it - let and loop get it for free as they don't need extra brackets to disambiguate, and for fn it's very helpful to be able to just chuck additional statements (debug prints, for example) at the top or bottom without having to wrap in (do). Plus it's free in the more-common single arity case, and keeping it around for multiple-arity keeps things internally consistent. On the other hand, if and cond would require disambiguating syntax to take additional statements regardless, and so that syntax might as well be (do). (... ([x] x) ([x x] x) ...); where there are complex evaluation rules...
and [x1 x2 x3], where all x are evaluated
and
[v1 e1 v2 e2 ...], where only e is evaluated, in LETand
[v1 ... vn], where no v is evaluated, in argument lists
etc., etc.I somehow fail to see the dramatic improvement over just using parentheses. Instead of learning building basic rules of forming and naming expressions with parentheses, I now learn a few inconsistent rules of forming and expressions with a set of delimiters - which is no problem, but it is not the huge progress you claim.
(let
([x 1]
[y 3])
(+ x y))
which is not too bad either.As I have written Racket code, I have found that square brackets get in the way. Don't misunderstand me, they look great when the are printed, but changing the internal structure of an expression requires changing concluding logic from '))])))' to ')))]))' that I've decided it's pain than gain. I'd rather just add another close parenthesis and move on to running tests than navigate character by character.
I love Racket, don't misunderstand me. But the square brackets are a faster horse at best, not a bicycle.
But how is this different from Clojure? You can have exactly the same problem there[1]. Whenever you introduce irregularity to the syntax you're going to have these issues. Clojure does it for "readability" and so does Racket. The difference is that in Racket you can opt-out and only use normal parens, while you can't do this in Clojure - which is probably fine in their respective cases, as they target a bit different audiences I think.
[1] But you do use an editor which makes this kind of problem impossible to occur, right? Like Emacs with Paredit or DrRacket with correct settings?
As I said it's complicated.
In Racket on the other hand `))))))` is equivalent to `)))]]]` except in so far as matching goes. The brackets are just decorations.
'(1 2 3)
constructs a value of type list, while this:
[1 2 3]
constructs a value of type vector.
They are not the same and you cannot say that one somehow becomes the other. And from what I remember Clojure does have a list data-type and it still needs to be quoted, except for empty list literal, (), which is self-evaluating.
So, in Clojure you need to quote your lists, exactly like in many other Lisps, and you have literals for other data structures, exactly like in many other Lisps ([] in Elisp, #() in Racket, CL covered by lispm). But of course Clojure is so much more readable because it has so few parentheses in comparison... to Java, I suppose.
Also
(let [my-list '(1 2 3)
my-vec [1 2 3]
(= my-list my-vec))
returns `true`. It's one of the subtleties of Clojure and its implementation on top of Java's object and type systems, and one which can be difficult to parse out at the lower end of the learning curve...which is where I am.Clojure is a member of Lisp family and it's a formidable and worthy member at that. But it's not as ground-breaking or unique as some people would like to think - the family is vast and multi-generational and many things were already tried in some form or the other.
I still like Clojure's particular view on Lispiness, though.
Finding a rationale for calling other people silly seems more like the point you were trying to make.
To the point of attributing statements and beliefs to me that I neither stated nor indicated I held.
The opening line of the first paragraph of your comment directly referred to the content of my post and the last word in that paragraph was silly.
Now understand I'm in my 20th year of internet use, so it's not the most uncivil thing that's ever been said to me. It's not even close to a rather mild incivility that I might have written a few years ago.
But it is uncivil and out of keeping with HN's community standards. There are plenty of other places that not only accept but tacitly encourage posts with that rhetorical flavor. But that's not HN.
The first was the mental conversion to/from f(a,b,c) to (f a b c) which is just moving the opening parenthesis one token to the left and seeing both commas and whitespace as "something between the tokens that really matter".
The remaining half was starting with Clojure. It is a Lisp whose constructs are really optimized towards dumping extraneous parentheses so it is easier not to get lost in the nesting levels.