Re: Cons vs List vs. ISeqs

Makes sense - Thanks (to all)! Tim On Jun 24, 8:29 pm, David Sletten wrote: > On Jun 24, 2011, at 7:35 PM, Tim Robinson wrote: > > > I'm under the impression that traditional lisps have a greater > > distinction between a cons operation vs. a list operation. > > Specifically I had believed that c

Re: A stupid jvm question

You might want to check this out: https://github.com/tinkerpop/tinkubator/tree/master/mutant -- You received this message because you are subscribed to the Google Groups "Clojure" group. To post to this group, send email to clojure@googlegroups.com Note that posts from new members are moderated -

Re: Cons vs List vs. ISeqs

I agree with David when he says that this is not really relevant. As a relative newbie to Lisps I have found that Clojure, while very Lispy in so many ways, is actually more different than I initially thought. It is really a hybrid of many languages wrapped in s expressions, which is what makes

Re: Clojure 1.3 Beta 1

What about juxt? Can we get rid of the "Alpha - name subject to change" in the docstring there? On Jun 24, 6:35 am, Aaron Bedra wrote: > Everything is now beta.  deftype/defrecord have had some changes > recently, but they are ready to rock.  I will update the docstrings today. > > Aaron > > On 0

Re: Clojure 1.3 Beta 1

On Fri, 24 Jun 2011 16:53:13 -0400, Stuart Sierra wrote: So, if you are currently using Clojure 1.2, your upgrade path might look something like this: 1. Find the "new" contrib library you need I am wondering how best to handle current contrib functionality, such as clojure.contrib.refl

Re: Can the namespace portion of a symbol contain slashes?

On Thu, Jun 23, 2011 at 11:54 PM, Meikel Brandmeyer wrote: > I'm sorry, but what is difficult about “it can be used *once*”. I understand > that as “there can be zero or one slashes in a symbol”. Everything else is an > invalid symbol and feeding it to the reader is undefined behaviour. The > r

Re: Cons vs List vs. ISeqs

On Jun 24, 2011, at 7:35 PM, Tim Robinson wrote: > I'm under the impression that traditional lisps have a greater > distinction between a cons operation vs. a list operation. > Specifically I had believed that consing was a more efficient and > better performing operation than using list. > Thi

Re: Cons vs List vs. ISeqs

It might be better to link to the main Clojure github repo for viewing the source in case things have changed since some random fork... https://github.com/clojure/clojure/blob/master/src/jvm/clojure/lang/Cons.java https://github.com/clojure/clojure/blob/master/src/jvm/clojure/lang/PersistentList.j

Re: Clojure 1.3 Beta 1

On Fri, Jun 24, 2011 at 1:53 PM, Stuart Sierra wrote: > The monolithic "clojure-contrib" project is not being actively maintained. > It does not currently build on Clojure 1.3 beta. All new development is > happening in "new" contrib libraries under http://github.com/clojure It's probably worth p

Re: Cons vs List vs. ISeqs

This stackoverflow page seems to have some info that might help: http://stackoverflow.com/questions/3008411/clojure-seq-cons-vs-list-conj Source for Cons: https://github.com/hiredman/clojure/blob/master/src/jvm/clojure/lang/Cons.java Source for PersistentList: https://github.com/hiredman/clojure/b

Cons vs List vs. ISeqs

I'm under the impression that traditional lisps have a greater distinction between a cons operation vs. a list operation. Specifically I had believed that consing was a more efficient and better performing operation than using list. Is this true? and if so, given both the Cons and Lists are actual

Re: [ANN] Pallet-Hadoop (Hadoop clusters as data structures)

Hey all, I've released an update to pallet-hadoop(0.3.0) that allows for spot instance support . The example cluster below, when run on EC2, chooses large instances; A large spot instance costs 12 cents an hour, do

Re: setting the classpath in cake+slime (was Re: Screencast: Clojure + Emacs + slime + swank + cake + Overtone)

Oops: Ignore my last "BTW" -- now load works for me too. Not sure why it didn't previously. I'd still like to know where it is specified that src and lib are on the classpath, but I guess I have everything working now. Thanks, -Lee On Jun 24, 2011, at 4:50 PM, Lee Spector wrote: > > Thanks

Re: Clojure 1.3 Beta 1

The monolithic "clojure-contrib" project is not being actively maintained. It does not currently build on Clojure 1.3 beta. All new development is happening in "new" contrib libraries under http://github.com/clojure Most of the libraries from "old" clojure-contrib have been released as "new" co

Re: setting the classpath in cake+slime (was Re: Screencast: Clojure + Emacs + slime + swank + cake + Overtone)

Thanks Gary. With this I'm able to get :use to work correctly -- FWIW the part I wasn't getting right (again :-() was the association between the namespace names and the directory structure. In the context of your example I was doing something like (ns core ...) rather than (ns overtone-test.co

Re: Clojure 1.3 Beta 1

What's the plan for a compatible version of clojure-contrib for 1.3? On Fri, Jun 24, 2011 at 9:47 AM, Mark Engelberg wrote: > One of the main changes to 1.3 is that arithmetic operations on longs > do not automatically overflow. > > In the early discussions of this new feature, it was pointed out

Re: setting the classpath in cake+slime (was Re: Screencast: Clojure + Emacs + slime + swank + cake + Overtone)

The way that cake and lein behave is generally this: 1) Search up the file tree starting from the directory in which cake or lein is called until a project.clj file is encountered. Consider this to be the project root. 2) Start a JVM in this directory with the classpath set to contain any files

Re: Clojure 1.3 Beta 1

One of the main changes to 1.3 is that arithmetic operations on longs do not automatically overflow. In the early discussions of this new feature, it was pointed out that people who want overflow capability can use the special "prime" operators, but that the preferred way to do things would be to

Strange Loop 2011 - St. Louis - Sept 18-20

I thought now would be a good time for an update here on the Strange Loop conference - http://thestrangeloop.com The early bird deadline is just 2 weeks away on July 8th, when the base price will go from $250 to $325. There are several Clojure-related workshops that are full or almost full: - Stu

Re: Help: Some AOT-compiled classes can't be required

> This creates a classes/midje/ directory full of class files. (QUESTION: Why > create a bunch of class files when Midje is in lib/ as a jar file?) leiningen's compile task calls clojure.core/compile for every namespace you specify in your project.clj. clojure.core/compile sets the *compile-files

Re: Conversion of one java example to clojure?

Sure could. And you don't want to do this if brownFox is a function: (Label. brownFox) If you really want it to be a function, you could do the following, but I think it would complicate things unnecessarily: (Label. (brownFox)) -- You received this message because you are subscribed to th

Re: Clojure 1.3 Beta 1

On 06/24/2011 09:29 AM, smf...@googlemail.com wrote: Just a quick question (before I forget): Is deftype/defrecord still alpha? Or is the "Alpha - subject to change" note in the docstrings just an oversight? Thanks, -F.M. I just created a housekeeping ticket around all of the alpha markings. S

Re: Clojure 1.3 Beta 1

Everything is now beta. deftype/defrecord have had some changes recently, but they are ready to rock. I will update the docstrings today. Aaron On 06/24/2011 09:29 AM, smf...@googlemail.com wrote: Just a quick question (before I forget): Is deftype/defrecord still alpha? Or is the "Alpha - s

Re: Clojure 1.3 Beta 1

Just a quick question (before I forget): Is deftype/defrecord still alpha? Or is the "Alpha - subject to change" note in the docstrings just an oversight? Thanks, -F.M. On 23 Jun., 20:43, Chris Redinger wrote: > Clojure 1.3 Beta 1 is now available at > > http://clojure.org/downloads > > All of y

Re: Conversion of one java example to clojure?

I am newbie. Could be better like this? (def brownFox "The quick brown fox jumps over the lazy dog.") -- You received this message because you are subscribed to the Google Groups "Clojure" group. To post to this group, send email to clojure@googlegroups.com Note that posts from new members are

Re: ANN: Hafni

Thanks for the interest! :) When it comes to arrows, from what I have read, functions can be seen as a subset to arrows. Although, I don't have sufficient understanding to what this really means. It's true that standard functions could be used, and would be clearer. I'm a little scared of doing t

Re: Generating API docs for clojure 1.3 projects

Tassilo Horn writes: Hi again, >> I'll try to get to that pretty soon so that you'll have something to >> use. I don't know why one you built should fail, but I haven't tried >> it myself. At first look, maybe it's the new numeric stuff or maybe >> it still has a bad dependency chain in it's pro

Re: Can the namespace portion of a symbol contain slashes?

Hi, Am 24.06.2011 um 09:13 schrieb B Smith-Mannschott: > Ah. Undefined behavior by virtue of the fact that it goes umentioned > in the documentation. How tautological. Alternately one could consider > explicitly documenting undefined behavior. I think that's why we were > talking past eachother.

Re: Can the namespace portion of a symbol contain slashes?

On Fri, Jun 24, 2011 at 08:54, Meikel Brandmeyer wrote: > Hi, > > Am 24.06.2011 um 01:59 schrieb Sean Corfield: > >> Which is the whole point: the docs ascribe meaning to a/b and to / but >> do not ascribe meaning to a/b/c > > I'm sorry, but what is difficult about “it can be used *once*”. I under