IMHO features expressions should be evaluated at read-time only.
Putting it off till the compilation phase only complicates things.
So I'm actually favoring a preprocessing step like here -
http://dev.clojure.org/display/design/Feature+Expressions?focusedCommentId=6390066#comment-6390066
The idea
Well, traditional transactions map to refs in Clojure.
You could use a ref, as in any transactional stuff must be performed
in a dosync
form.
However, using a agent is a much cleaner solution for your needs IMHO.
An agent, by definition, can be executing only one operation at a given
time, and
Re: this Snapshot thing - it's not very convenient for me to work this
way as I need to be online for Leiningen to pull down the updates. I
understand that it's possible to freeze the snapshot so I can keep a single
stable copy in .m2, but how is this done...?
--
--
You received this message
(Thanks Konrad; a nice summary.)
On Thursday, March 7, 2013 7:28:57 AM UTC, Konrad Hinsen wrote:
My latest article in Computing in Science and Engineering, with example
code in Clojure, in free access for a while:
A Glimpse of the Future of Scientific Programming
noir-auth-app is a complete authentication web app based on Compojure,
lib-noir, Enlive and CongoMongo. It also uses a bit of ClojureScript, jayq
and shoreleave-remote.
It's meant to be used as a base app for building Clojure web apps that
require authentication.
Isn't it possible to solve this with a simple macro?
(case-dialect
:clojure (... clojure code ...)
:clojurescript (... clojurescript code ...))
Then, in jvm clojure, it could be implemented as:
(defmacro case-dialect [ {:keys [clojure]}] clojure)
and in clojurescript:
(defmacro
I may be wrong, but I think this, and anything else that tries to solve
this problem after read time, will fail for one of the primary uses of
feature macros: Java packages/namespaces that exist for Clojure/JVM but not
ClojureScript, and JavaScript namespaces that exist for ClojureScript but
not
Use mongo findandmodify command. Only way I know
On Mar 6, 2013 8:36 AM, bruce li leilmy...@gmail.com wrote:
Hello,
I'm working on a piece of code that uses congomongo to access mongodb.
What I want to implement is to use one collection of the DB as a
queue(let's say, it's called task).
Hi,
On Wednesday, March 6, 2013 2:53:26 PM UTC+1, Alan Busby wrote:
With the release of Clojure 1.5 and it's new reducers, I figured this
would be a good time to release a library to help with file IO for
reducers. As reducers can only operate in parallel over specific
collections, like
I have not read all of the discussions about this topic, so I
apologize if it has already been discussed, but I was wondering why
there does not seem to be any discussion about the openness of such a
system. As far as I know, CL-style feature expressions are closed in
the same sense that a cond
Class names are read in as symbols
On Mar 7, 2013 7:10 AM, Andy Fingerhut andy.finger...@gmail.com wrote:
I may be wrong, but I think this, and anything else that tries to solve
this problem after read time, will fail for one of the primary uses of
feature macros: Java packages/namespaces that
At some point on this mailist, someone suggested that to best understand
concurrency in Java, once should read:
Java Concurrency In Practice
http://www.amazon.com/Java-Concurrency-Practice-Brian-Goetz/dp/0321349601/ref=sr_1_1?ie=UTF8qid=1362688125sr=8-1keywords=java+concurrency+in+practice
The macro doesn't have that problem - as long as the code is inside the
macro.
I.e. this works (in clojure):
(case-dialect :clojurescript some.class/PROP)
But this doesn't:
(defn get-PROP [] some.class/PROP)
(case-dialect :clojurescript (get-PROP))
If I'm not mistaken, the proposed expressions
I did a board on clojure performance, if you'd like check it out. Hopefully
it
helps. http://www.verious.com/board/AKumar/improving-performance-with-clojure/
On Monday, February 18, 2013 8:16:51 PM UTC-8, Geo wrote:
Hello,
I am cross-posting my Clojure question from StackOverflow. I am
On Mar 8, 1:32 am, larry google groups lawrencecloj...@gmail.com
wrote:
At some point on this mailist, someone suggested that to best understand
concurrency in Java, once should read:
Java Concurrency In Practice
http://www.amazon.com/Java-Concurrency-Practice-Brian-Goetz/dp/032134...
So
From what I understand, the reader will call the tag function, thus being
executed at read time and not compile time.
On Thursday, March 7, 2013 4:04:15 AM UTC-5, Akhil Wali wrote:
IMHO features expressions should be evaluated at read-time only.
Putting it off till the compilation phase only
Hi,
Very nice work. I'm interested in using graph but just curious in terms of
your priorities for future development.
I noticed that you listed as a todo, you might want to save the body of a
fnk which I see as a potential for inlining the bodies and thus eliminating
the fn call when
17 matches
Mail list logo
