Yep... my presentation proposal went in last week...
http://skillsmatter.com/event/scala/clojure-exchange
and
http://skillsmatter.com/event/scala/clojure-exchange-2012
Indeed; sign up now for what promises to be the best Scala event of 2012.
-- N.
--
You received this message because
Here's a simple protocol/deftype example:
(defprotocol FOO
(doit [this]))
(deftype Foo [_arg]
FOO
(doit [this] nil))
(deftype Foo [__arg]
FOO
(doit [this] nil))
The first definition of Foo compiles; the second gives
(class: user/Foo, method: create signature: (Lclojure/lang/
This is straight from the doc string:
(with-out-str (p/prxml [:p {:class greet} [:i Ladies
gentlemen]]))
Works in Clojure 1.2.1:
(:ok \p class=\\\greet\\\iLadies amp; gentlemen/i/p\)
(that's pasted from the slime event buffer, hence the superfluous
armour.)
Fails in Clojure 1.3.0:
Ah: found this thread:
https://groups.google.com/forum/#!topic/clojure-dev/IGD6Ziqt-QY
So: would still be very obliged for a link to an XML-generating
package working under 1.3.0. (I don't need to parse.)
--
You received this message because you are subscribed to the Google
Groups Clojure
Nice work. Perhaps it's getting to be time to retire my own Java OSC
library...
Is this reachable via Lein/Maven?
-- N.
--
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
On Jul 29, 1:18 am, Ken Wesson kwess...@gmail.com wrote:
On the one hand, assuming that Java 7 doesn't outright break anything, [...]
Like loops?
http://www.lucidimagination.com/blog/2011/07/28/dont-use-java-7-for-anything/
--
You received this message because you are subscribed to the Google
Clojure newcomer here, but here's the thought that's frontmost in my
mind about ClojureScript...
I'm used to Clojure as a language that's solidly spot-welded to the
JVM and the Java libraries. Just as [1 2 3] is legal portable
Clojure code, so is (.start (Thread. #(...))) despite it being a
Hi Sam,
A nice late night exercise...
Not very practical, but if you want a safe transaction-free operation
on an atom which returns whether it was changed, you can perhaps hack
it by embedding the change state into the atom itself:
(def a (atom {:value 45 :changed? false}))
(defn
Of course, once posted, I realised the conditional could be
eliminated:
(defn update-and-check-whether-modified?
[update-fn]
(:changed?
(swap! a (fn [{v :value _ :changed?}]
(let [new-v (update-fn v)]
{:value new-v :changed? (not= v new-v)})
--
You
(Have just found the leiningen google group - will post there - sorry
for the noise.)
-- N.
--
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 -
This must be something really stupid I'm doing...
If I run a vanilla clojure repl via java -jar clojure-xxx.jar, then
agents do what I'd except. Ditto using Leiningen's generated
standalone swank-clojure server.
If I do a lein repl or connect to a lein swank in a simple
project, then agents
11 matches
Mail list logo
