On Thu, 10 Feb 2011 21:57:01 -0800
Sean Corfield wrote:
> Agreement pretty much identical to the Clojure / Oracle CA (with the
> only exception to the process being that they will allow scanned,
> signed CAs to be emailed to the project team).
That exception is the major issue, assuming you don'
On Feb 16, 2:01 am, Michael Sanders wrote:
> I think I've worked out a better solution (hope this post renders properly):
>
> (ns topic (require [clojure.string :as s]))
>
> (defn load-block
>
> "TOPIC database: prints associated blocks to stdout"
>
> ([tag]
> (let [STATE (atom 0)
>
On Thu, 17 Feb 2011 10:26:05 -0800 (PST)
JMatt wrote:
> On Feb 16, 10:29 pm, Andreas Kostler
> wrote:
> > Is there an easy and idiomatic way of getting the digits of a number in
> > clojure?
> Here is my attempt at this from a few months ago:
My turn...
(defn to-digits
"Create a seq of digit
On Thu, 17 Feb 2011 15:27:47 -0600
Michael Gardner wrote:
> On Feb 17, 2011, at 1:36 PM, Mike Meyer wrote:
>
> > My turn...
> >
> > (defn to-digits
> > "Create a seq of digits from a number."
> > [i]
> > ^{:user/comment "For Euler Pr
On Tue, 22 Feb 2011 15:36:02 -0800 (PST)
Daniel Bell wrote:
> I can't think of anything core, but
>
> (let [f #(. % toUpperCase)]
> (zipmap (keys skills) (map f (vals skills doesn't seem too bad.
Does clojure guarantee that keys & vals return things in the proper
order for this to work? S
On Tue, 22 Feb 2011 16:23:00 -0800 (PST)
Alan wrote:
> Yes, it is guaranteed, and I'm dubious about your claim about
> serializing. (seq foo) will return the entries in foo in the same
> order always; but (seq (assoc foo 1 2)) may return the entries in a
> completely different order. You can trea
301 - 306 of 306 matches
Mail list logo
