This isn't really right. :source-paths are for your _sources_, not a
place to drop in whatever paths you want either on the classpath or
included in jar files, etc. Also, all generated content should go into
`target/*`, so that `lein clean` will have its intended effect
(eliminating all
Hi Chas, thanks for the clarification--it was definitely not clear to me
how this worked so I appreciate the explanation.
Regarding the PR, I suppose the same points you brought up here are
relevant there, since I proposed including my (mistaken) notion of how
source-paths work for cljx-based
Here's an open source datalog for clojure:
https://github.com/tailrecursion/bacwn
2014-02-14 7:38 GMT+01:00 t x txrev...@gmail.com:
@David:
* set operations is not what I'm looking for
* the relational algebra blog was very useful
@Jeb:
* Ha! I didn't know that q could be used
I've added a sample.project.clj file to the cljx repo and pointed to it
from the README. I can see how the confusion may have gotten started
due to a particular detail in the example configuration snippet that was
in the README, which is also fixed.
If someone wants to submit a patch so that
Awesome!
I was needing something like om-sync in an app I'm building. Have to try it
ASAP.
Om is really nice to work with, so thanks for all your work on it! :)
--
You received this message because you are subscribed to the Google
Groups Clojure group.
To post to this group, send email to
Btw, I seem to get the following compiler errors after upgrading om from
0.3.6 to 0.4.0
(clojurescript version is 0.0-2138)
WARNING: Use of undeclared Var om.core/specify! at line 570 out\om\core.cljs
WARNING: Use of undeclared Var om.core/_ at line 572 out\om\core.cljs
WARNING: Use of
Om 0.4.0 requires ClojureScript 0.0-2156, also looks like you need to run a
`lein cljsbuild clean`.
David
On Fri, Feb 14, 2014 at 8:00 AM, Tatu Tarvainen tatu.tarvai...@mac.comwrote:
Btw, I seem to get the following compiler errors after upgrading om from
0.3.6 to 0.4.0
(clojurescript
I'd love to see someone tackle a NetBeans plugin (see parallel thread in
which I point out non-existent alternatives and point out that it supports
Scala well -- something we should address if we're to expand mindshare).
--
You received this message because you are subscribed to the Google
Hi there,
I've been using LightTable daily (and vim) for my Clojure stuff, but I'm
now finding myself having to use NetBeans in order to better manage a
number of existing Java-related sub-projects.
It's not a matter of language choice, but of environment uniformity (I need
to use the same
@Chris
thanks :-) Nothing public yet, I've got a few odds and ends I'd like to
tie up first. Am looking to get it up on Github next week, or early the
week after, and will be sure to post a message to the list once it's there
:-)
Jony
On Thursday, 13 February 2014 23:53:59 UTC,
Hi!,
Aviso is looking for Clojure developers to work on Novate, our Electronic
Funds Transfer (EFT) payments switch.
When it's at home, an EFT payments switch is responsible for providing
connectivity for real-time messaging between the different parties involved
in electronic payments
As a Xmas present I gave myself a copy of Concepts, Teechniques and Models
of Computer Programming and I'm enjoying myself reading it. The book uses
Oz/Mozart but I'm trying to translate some of the code in clojure.
The first computation model is declarative and variables behave much as
LVars
You will need to implement unification for your record type. I recommend
just using simpler data structures unless how to do this is apparent to you
- it's not particularly difficult but you need to go to the source if you
want to understand how to make it work.
David
On Fri, Feb 14, 2014 at
Clojure 1.6.0-beta1 is now available.
Try it via
- Download: http://central.maven.org/maven2/org/clojure/clojure/1.6.0-beta1
- Leiningen: [org.clojure/clojure 1.6.0-beta1]
Highlights below or see the full change log here:
https://github.com/clojure/clojure/blob/master/changes.md
We expect
Great changes! I have a question about #5.
5) New some operations
Many conditional functions rely on logical truth (where falsey
values are nil or false). Sometimes it is useful to have functions
that rely on not nilness instead. These functions have been added to
support these cases
Looking forward to this ... any ideas on submitted issues w/ valid patches
that are in limbo? (*)
(*) No good deed, such as this beta release announcement, goes unpunished.
--
You received this message because you are subscribed to the Google
Groups Clojure group.
To post to this
Awesome! Thanks!
2014-02-14 21:47 GMT+01:00 Daniel doubleagen...@gmail.com:
Thanks to everyone involved!
On Friday, February 14, 2014 1:04:09 PM UTC-6, Alex Miller wrote:
Clojure 1.6.0-beta1 is now available.
Try it via
- Download: http://central.maven.org/maven2/org/clojure/
Hi all,
As a follow-up to this post -
https://groups.google.com/forum/#!topic/clojure/B7dTW5PDcPM,
it's now possible to jump to any Clojure tag in current directory.
No project definitions required: CEDET will parse every source file in
current directory.
The tags are completed with helm
t x txrev...@gmail.com wrote:
@David:
* set operations is not what I'm looking for
Just in case you didn't notice it (it's not called out very prominently), when
the `clojure.set` documentation [1] mentions a rel it's referring to a set of
maps - a table similar to what you mentioned.
[1]
On Friday, February 14, 2014 5:00:10 AM UTC-8, Tatu Tarvainen wrote:
Btw, I seem to get the following compiler errors after upgrading om from
0.3.6 to 0.4.0
(clojurescript version is 0.0-2138)
WARNING: Use of undeclared Var om.core/specify! at line 570 out\om\core.cljs
WARNING: Use
+1 to everything Dom Kiva-Meyer said.
On Fri, Feb 14, 2014 at 2:13 PM, Andrey Antukh n...@niwi.be wrote:
Awesome! Thanks!
2014-02-14 21:47 GMT+01:00 Daniel doubleagen...@gmail.com:
Thanks to everyone involved!
On Friday, February 14, 2014 1:04:09 PM UTC-6, Alex Miller wrote:
Clojure
exists? doesn't seem right to me. Also we do use `exists?` currently in
ClojureScript since feature detection is so common in client side code and
the name seems more appropriate to me in that context. That could of course
change but we would need to coordinate.
David
On Fri, Feb 14, 2014 at
Dom Kiva-Meyer li...@domkm.com writes:
5) New some operations
Many conditional functions rely on logical truth (where falsey
values are nil or false). Sometimes it is useful to have functions
that rely on not nilness instead. These functions have been added to
support these cases [CLJ-1343]:
I would also like to point out that `if-some` reads like it would work
like `if-not` rather than like `if-let`.
Same applies obviously to `when-some` too.
Timothy Baldridge writes:
+1 to everything Dom Kiva-Meyer said.
On Fri, Feb 14, 2014 at 2:13 PM, Andrey Antukh n...@niwi.be wrote:
Also I think the ship on overloading some already sailed with some- and
some-
David
On Fri, Feb 14, 2014 at 3:27 PM, Dom Kiva-Meyer li...@domkm.com wrote:
Great changes! I have a question about #5.
5) New some operations
Many conditional functions rely on logical truth (where falsey
Hey Howard,
Same story as always - when we moved into the 1.6 release train, we
basically stopped putting new tickets into work so that we could stabilize
the release. That process has taken longer than I expected.
My expectation is that:
1) All of you will try out 1.6.0-beta1 as soon as
On Friday, February 14, 2014 2:27:49 PM UTC-6, DomKM wrote:
Great changes! I have a question about #5.
5) New some operations
Many conditional functions rely on logical truth (where falsey
values are nil or false). Sometimes it is useful to have functions
that rely on not nilness
On Feb 14, 2014, at 17:25 , Alex Miller a...@puredanger.com wrote:
The names of these functions were chosen by Rich. There was already some name
overloading of some even before these new functions with some (truthy) and
some-/some- (not nil). The new functions keep with the latter meaning.
As an addendum to my last comment, *not-nil?* would also be a good
candidate. That really doesn't leave room for doubt.
This:
(some? false) ;; = true
Would confuse me. On the other hand this:
(not-nil? false) ;; = true
Would not.
There's really no need to complicate the naming story
exists? is a pretty critical feature for application writers and I asked
several users about it before committing to a name. Unless Clojure decides
to adopt it, little incentive to cause unnecessary breakage.
David
On Fri, Feb 14, 2014 at 10:28 PM, Joel Holdbrooks cjholdbro...@gmail.comwrote:
Hi, I'm writing some queries using java.jdbc 0.3.3 as follows:
(defn get-member-url [id]
(jdbc/query db [SELECT * FROM members WHERE id = ? LIMIT 1 id]))
However this results in an exception error:
java.lang.ClassCastException
clojure.lang.LazySeq cannot be cast to clojure.lang.IFn
Not sure
Likely discussed in #clojure IRC and I checked with some Clojure/core folks
for feedback.
David
On Fri, Feb 14, 2014 at 10:54 PM, Joel Holdbrooks cjholdbro...@gmail.comwrote:
Right. I won't disagree with the function being critical or with avoiding
breakage. I'm just mostly whining here
Could someone clarify for me why some? as a name for not nil makes sense
at all in the first place? Not criticizing. I just don't understand what
existence or there being some of something has to do with nil.
Maybe I don't understand the intent of nil. I came to Clojure from Common
Lisp.
On Fri, Feb 14, 2014 at 9:41 PM, Mars0i marsh...@logical.net wrote:
Could someone clarify for me why some? as a name for not nil makes sense
at all in the first place? Not criticizing. I just don't understand what
existence or there being some of something has to do with nil.
nil is often
2014-02-15 7:55 GMT+04:00 The Dude (Abides) exel...@gmail.com:
However this results in an exception error:
java.lang.ClassCastException
clojure.lang.LazySeq cannot be cast to clojure.lang.IFn
Please post a complete stack trace.
--
MK
http://github.com/michaelklishin
35 matches
Mail list logo
