When I try to use core.logic's fact function I am getting a symbol not found
error. What is the idiomatic way to do something like:
(logic/fact Orbits :mercury :sun)
Orbits here was previously bound in a defrel, which I ended up replacing with
pldb/db-rel.
*example from Joy of Clojure's
On 9 June 2014 02:03, gvim gvi...@gmail.com wrote:
(ns gh1.tmp
(:require [clj-commons-exec :as exec]
[clj-time.core :as t]))
(defn calc [day month year hour min sec zone]
(let [bin /Users/zephyr/html/astro/bin/swetest
data (str -p0123456789t -fPZl -b
Then why does this work when executed manually in the shell?
./swetest -p0123456789t -fPZl -b14.10.1960 -ut13:45 -roundmin
-head -true -eswe
gvim
On 09/06/2014 08:21, Ray Miller wrote:
On 9 June 2014 02:03, gvim gvi...@gmail.com wrote:
(ns gh1.tmp
(:require [clj-commons-exec :as
On 9 June 2014 12:39, gvim gvi...@gmail.com wrote:
Then why does this work when executed manually in the shell?
./swetest -p0123456789t -fPZl -b14.10.1960 -ut13:45 -roundmin -head
-true -eswe
I suspect exec/sh is expecting a list of options. The way you are
calling it, swetest is called
Yes, by using externs:
http://lukevanderhart.com/2011/09/30/using-javascript-and-clojurescript.html
A bit dated, but I think this is still the way to go!
/Linus
2014-06-08 6:36 GMT+02:00 Gabrien phuthuycuoimayhut...@gmail.com:
Is there any way to use nodejs modules (the browserifiable ones)
Here are some functional programming job opportunities that were posted
recently:
Sr. Software Engineer at Clutch Analytics
http://functionaljobs.com/jobs/8720-sr-software-engineer-at-clutch-analytics
Cheers,
Sean Murphy
FunctionalJobs.com
--
You received this message because you are
On 09/06/2014 14:04, Ray Miller wrote:
I suspect exec/sh is expecting a list of options. The way you are
calling it, swetest is called with only two arguments (data and
flags). When you type the command at the shell, the shell splits on
whitespace before invoking exec, so it sees 8 arguments.
Hi David, this is great! I've switched to this branch, updated all hashing
impls of deftypes in my library and it works without a hitch and see much
less hash collisions in large 3d meshes as a result. Awesome!
K.
On 8 Jun 2014 18:07, David Nolen dnolen.li...@gmail.com wrote:
1.6.0 branch is
That's great to hear, the feedback is much appreciated.
David
On Mon, Jun 9, 2014 at 1:06 PM, Karsten Schmidt i...@toxi.co.uk wrote:
Hi David, this is great! I've switched to this branch, updated all hashing
impls of deftypes in my library and it works without a hitch and see much
less hash
Starting today, we have updated the Clojure Contributor Agreement process.
The prior process which involved signing and mailing a form has been
replaced with an online e-signing process.
Existing contributors that have signed the Contributor Agreement are
unaffected - those agreements are still
2014-06-09 21:23 GMT+04:00 Alex Miller a...@puredanger.com:
Starting today, we have updated the Clojure Contributor Agreement process.
The prior process which involved signing and mailing a form has been
replaced with an online e-signing process.
\o/
--
MK
http://github.com/michaelklishin
metrics-clojure [1] is a Clojure interface to the Metrics library [2].
2.0.3 is a bug fix release:
https://github.com/sjl/metrics-clojure/blob/stable/ChangeLog.md#changes-between-202-and-203
If you are not sure why gathering metrics about your apps and infrastructure
is a big deal, consider
\o/
On Mon, Jun 9, 2014 at 3:34 PM, Michael Klishin
michael.s.klis...@gmail.com wrote:
2014-06-09 21:23 GMT+04:00 Alex Miller a...@puredanger.com:
Starting today, we have updated the Clojure Contributor Agreement process.
The prior process which involved signing and mailing a form has been
Very nice! \o/
2014-06-09 20:57 GMT+02:00 Plínio Balduino pbaldu...@gmail.com:
\o/
On Mon, Jun 9, 2014 at 3:34 PM, Michael Klishin
michael.s.klis...@gmail.com wrote:
2014-06-09 21:23 GMT+04:00 Alex Miller a...@puredanger.com:
Starting today, we have updated the Clojure Contributor
I hope this isn't frowned upon here, but here goes.
I'm looking for freelance work while I figure out my next startup. Until
recently, I was Founder CTO of a startup of 10 engineers, the product is
100% Clojure (except for the UI, which was transitioning from Coffeescript
to Clojurescript).
On Mon, Jun 2, 2014 at 6:54 AM, John Gabriele jmg3...@gmail.com wrote:
On Sunday, June 1, 2014 5:15:52 PM UTC-4, Andy Fingerhut wrote:
Thanks to Francois du Toit, the versions of the Clojure cheatsheet
available at the link below now have the ability to let you search for all
symbols
I once liked the Clojure's less-parentheses approach.
Today I found that you can't utilize s-expression comments easily in
Clojure.
e.g.
In
(let [x 1 y 2] x)
When you are about to comment out the y 2 part, you have to move the
cursor back and forth to insert new parentheses.
And you can't
Thank you, Mark and Mike
Awesome explanation and examples
Plínio
On Sat, Jun 7, 2014 at 8:46 AM, Mike Fikes mikefi...@me.com wrote:
Thanks for the historical perspective, puzzler!
In addition to performance considerations, Clojure Programming points to an
inconsistency between hash codes
On Mon 9 Jun 2014 at 07:07:42PM -0700, Taegyoon Kim wrote:
And you can't do this:
user= (let [x 1 (comment y 2)] x)
Alex Miller (?) once pointed out that the #_ reader macro can be chained
like this:
(let [x 1 #_#_y 2] x)
Pretty nifty.
guns
pgpn7C26ipuE0.pgp
Description: PGP signature
On Jun 9, 2014, at 7:07 PM, Taegyoon Kim stelofl...@gmail.com wrote:
And you can't do this:
user= (let [x 1 (comment y 2)] x)
You can, however, do this:
user= (let [x 1 #_(y 2)] x)
and this:
user= (let [x 1 #_y #_2] x)
Sean Corfield -- (904) 302-SEAN
An Architect's View --
Ah, reader macro! Thanks!
Ignore next form (#_)
The form following #_ is completely skipped by the reader. (This is a more
complete removal than the *comment*
http://clojure.github.io/clojure/clojure.core-api.html#clojure.core/comment
macro which yields nil).
(from
I have compilation warnings related to core.async. Here is the log:
Compiling resources/public/js/main.js from [src/cljs]...
Jun 10, 2014 7:49:49 AM com.google.javascript.jscomp.LoggerErrorManager println
WARNING:
/Users/viebel/libs/klozzer/target/cljsbuild-compiler-0/cljs/core/async.js:127:
The only place I've found the comment macro to be useful is at the
top-level of a ns to hold a bunch of test/temp code.
On Monday, June 9, 2014 11:22:10 PM UTC-5, Taegyoon Kim wrote:
Ah, reader macro! Thanks!
Ignore next form (#_)
The form following #_ is completely skipped by the reader.
Re the initial implicit question about appropriateness...
In my opinion, my opinion is that this group is for Clojurists to discuss
things of interest to Clojurists. Postings for Clojure jobs or Clojure
skills for hire fits into that category. At the present moment, the
frequency of such posts
Greetings!
I'm pleased to announce the release of Leiningen 2.4.0, our most
significant release in quite some time. The star of the show is the new
`release` task, which can automate all the common steps behind the
release of a new version of a library.
The idea is that `lein release` will run
Looks like new warnings from the Closure Compiler - something for
core.async to address. Thanks for the report!
David
On Tue, Jun 10, 2014 at 12:55 AM, Yehonathan Sharvit vie...@gmail.com wrote:
I have compilation warnings related to core.async. Here is the log:
Compiling
26 matches
Mail list logo
