Re: Road to Clojure Survey

On Feb 21, 6:57 am, Pascal Costanza <p...@xxxxxxxxx> wrote:
Helmut Eller wrote:
* Vend [2009-02-20 22:26+0100] writes:

FSet is a library, not a language.
If I understand correctly, native immutable collections are just one
feature of Clojure, and it integrates well with other features
(polymorphic collection manipulation and concurrency control).

I'm confused by this whole discussion.

Aren't Clojure's collection classes just a library and the Clojure
compiler/language treats them just like any other Java class? Is there
a reason why those classes could not be used in normal Java programs?

They can be used in Java, but you have to adapt your programming style.
Existing Java code will not just automagically work with them in the
general case.


This is FUD - please stop spreading it.

Rich
.

Relevant Pages

  • Re: Road to Clojure Survey
    ... native immutable collections are just one ... feature of Clojure, and it integrates well with other features ... a reason why those classes could not be used in normal Java programs? ... before he switched to Common Lisp, and his first writings on Common ...
    (comp.lang.lisp)
  • Re: Reddit Guys on the Pros and Cons of Lisp
    ... >> I never have to do that with Java. ... > language features, etc. ... They either have the feature or they don't. ... > libraries doing almost the same - for those languages. ...
    (comp.lang.lisp)
  • Re: 7.0 wishlist?
    ... The primary purpose of unchecked conversions is to facilitate migration to generics at disparate times. ... Operator overloading is principally used for mathematical constructs. ... It is not the job of the language designer to enforce against every conceivable misuse of a language feature, least of all to do so by simply refusing to add any features at all for fear that they might otherwise be abused. ... it is difficult for Java to not have chosen C++ syntax for various reasons. ...
    (comp.lang.java.programmer)
  • Re: the Java Lang will support Properties in Futuere?
    ... the fact that some other language has a feature isn't a reason to include it in Java per se. ... setPropertyA ... A second cost is that property support makes name resolution--a difficult step already--somewhat more difficult. ...
    (comp.lang.java.programmer)
  • Re: Java type-casting -- Q3
    ... Java doesn't have any grammar or syntax for that scenario now. ... You also have to make sure those modifications don't interfere with existing language features, nor would interfere with other more important language features that may come about in the future. ... And then you have to implement all that in a completely bug-free way in the compiler, and possible the run-time itself depending on how deeply ingrained the feature is. ... If you want variable-length type parameter lists in generics, you are easily talking up to a year, or more, of design and development work. ...
    (comp.lang.java.programmer)