Clojure

What does /prog/ think about Clojure? I'm in the process of learning it and it's pretty nice.

I'll just leave this here

? (defun id (x) x)
Error: Error reporting error
While executing: CCL::FUNCALL-WITH-ERROR-REENTRY-DETECTION, in process listener(1).
Type :POP to abort, :R for a list of available restarts.
Type :? for other options.
1 >

I think it looks like a promising new Lisp, but I dont like that it runs off the Java VM, Id like to see a stand-alone implementation of it

>>2
That's Clozure, not Clojure, also it works just fine here:

? (defun id (x) x)
ID
? (id #'id)
#<Compiled-function ID #x8ABCF96>

>>3
Id like to see a stand-alone implementation of it
What the _f^u_c^k does that mean?

Also there is a preliminary CLR implementation.

>>5
Are you stupid?
I dont like that it runs off the Java VM

>>6
You didn't answer my question. What the FUCK does ``stand-alone implementation'' mean?

[spoiler][b]_ARE[sup]YOU[/sub] STUPID?[/sub][/b][/spoiler]

>>7
You didn't answer my question. Are you stupid?

>>8
I asked first.

>>9
WHBTEO

http://4-ch.net/code/kareha.pl/1223551787/6

>>11
the guy who wrote that post is missing the idea of clojure. The WHOLE idea of clojure is to make all data structures immutable and therefore make concurrency very easy. So data structures never get changed in clojure but rebuilt into new ones. So clujure is a Lisp that is moving toward the direction of Erlang

>>12
>So clujure is a Lisp that is moving toward the direction of Erlang
Sounds almost too good to be true.

>>13
You could just use Erlang.

>>14
You could just use Erlang and don't say again you could just use Erlang.

>>15
EXPERT SEPPLES PROGRAMMER
(Your grammar is undecidable.)

>>3
Running on the JVM is an advantage of Clojure, you get a giant selection of libraries available to you.

>>17
Thats a *selling point* not an advantage. More people might be inclined to try clojure knowing that there are already a large base of libraries. But that also holds back the language since Java is a VM based OO language used by a functional language that is restrained by what is provided in the Java API. It cant do things as simple as tail recursion optimizations. If clojure were implemented in C as most other compilers, than you have a more machine specific implementation to run on different platforms

>>18
If clojure were implemented in C as most other compilers,
Most Lisps are implemented in Lisp, and usually compile to native code, however the GC tends to be written in C most of the time.

>>18
Thats a *selling point* not an advantage.
QFT. I feel strongly that library completeness is important and therefore advantageous, but I've always found relying on a bulk of foreign libraries nothing short of hell.

>>18

It cant do things as simple as tail recursion optimizations

It can do tail recursion optimization, although loop/recur is a bit of a hack.

If clojure were implemented in C as most other compilers, than you have a more machine specific implementation to run on different platforms

Java, and by extension clojure, already runs on all major operating systems and a lot of phones so unless you meant running clojure on embedded systems I don't see the problem.

>>21
more specific
He seems talking about compiling to native code, or something. Or maybe he just wants to avoid the atrocious results you get when you bland down your language<->platform integration to the degree Java does.

Bumping a thread about programming.

>>18
If clojure were implemented in C as most other compilers, than you have a more machine specific implementation to run on different platforms

I'm not sure if this is talking about a clojure VM (wouldn't JVM count then?) or a clojure compiler. The latter, with out any further work, would only give you access to more native compilers--which spit out code for the original target. (Still JVM?)

>>23
admittedly things get blurry when defining the difference between a VM and maching compiled compiler both in respect to the JVM and Lisp. Lisp is primarily written in itself, what the base language of its primitive contructs is not of much importance. Even though its interpreted it gets compiled to machine code. And some might say that a C compiler is giving the same results as a VM would, its just giving cross-platform translation, the difference being that the JVM has a layer sitting on top of that abstraction of a full language and libraries. So what Im trying to say it that Im not trying to shoot down the idea of the JVM as a base for common compiler design, its a very valid concept for eliminating needless repitition between languages