Re: leiningen: RuntimeException: Unable to resolve symbol: doc in this context

2012-10-27 Thread AtKaaZ
I believe I've hit this with 1.5.0-alpha6 or so(or maybe i was using the master branch) in eclipse+ccw after a while in repl: doc and source wouldn't work like you described and I'd have to (use 'clojure.repl) But in the same repl session worked a few minutes before. Do you think this commit fixes

Re: Bug in CLJS compiler?

2012-10-27 Thread David Nolen
On Sat, Oct 27, 2012 at 8:19 AM, Tim wrote: > While playing around with a little test website I came across what, I > believe to be a bug in the CLJS compiler. It seems like the generation of > symbols for use in macros (e.g. var#) is broken when compiled into certain > JavaScript forms. > This

Re: CLJS: println stopped working (r1514) ?

2012-10-27 Thread David Nolen
On Tue, Oct 23, 2012 at 4:18 PM, Frank Siebenlist < frank.siebenl...@gmail.com> wrote: > Bump. > > Could someone please confirm that printing from the repl doesn't work > anymore? > > Thanks, Frank. I just checked browser REPL on CLJS master - it works fine for me. David -- You received this

Re: leiningen: RuntimeException: Unable to resolve symbol: doc in this context

2012-10-27 Thread Marek Šrank
Oh yes, I've found the commit https://github.com/clojure/clojure/commit/728972b026a323fc941a5d560b81d37453dc6cad . I should look at the commits first Marek. On Saturday, October 27, 2012 10:26:22 PM UTC+2, Marek Šrank wrote: > > Please ignore that github link. I somehow got the feeling

Re: leiningen: RuntimeException: Unable to resolve symbol: doc in this context

2012-10-27 Thread Marek Šrank
Please ignore that github link. I somehow got the feeling that it's about a bug in leiningen (really don't know why :), but now I see that it's (probably) totally unrelated :D Marek On Saturday, October 27, 2012 10:20:34 PM UTC+2, Marek Šrank wrote: > > When using [org.clojure/clojure "1.5.0-bet

leiningen: RuntimeException: Unable to resolve symbol: doc in this context

2012-10-27 Thread Marek Šrank
When using [org.clojure/clojure "1.5.0-beta1"] in my project.clj, calling: (doc function) gives me this exception: CompilerException java.lang.RuntimeException: Unable to resolve symbol: doc in this context, compiling:(NO_SOURCE_PATH:1:1) And similarly with find-doc, source, javadoc and clojure

ANN: data.json 0.2.1 and tools.namespace 0.2.1

2012-10-27 Thread Stuart Sierra
[org.clojure/data.json "0.2.1"] * restores deprecated API functions from 0.1.x releases * recommended over 0.2.0, which broke code that depended on the old API [org.clojure/tools.namespace "0.2.1"] * minor bugfix * restores deprecated API functions from 0.1.x releases * recommended over

Re: with-open and line-seq

2012-10-27 Thread Devin Walters
Yeah, `read-lines` is what I was referring to. -- Devin Walters On Friday, October 26, 2012 at 9:10 PM, Andy Fingerhut wrote: > Devin, did you mean read-line from the old clojure.contrib.io > (http://clojure.contrib.io)? > > http://clojuredocs.org/clojure_contrib/clojure.contrib.io/read-lin

Re: monads

2012-10-27 Thread Armando Blancas
I found these articles very valuable in understanding the original motivation for monads and their use for practical development. Imperative Functional Programming Simon Peyton Jones, Philip Wadler http://research.microsoft.com/pubs/67066/imperative.ps.z Monadic Parser Combinators Graham Hutton

Re: core.logic and other types of solvers

2012-10-27 Thread David Nolen
On Sat, Oct 27, 2012 at 12:11 AM, Brandon Bloom wrote: > I'd suspect the specialized solvers provide performance > and predictability tuned to their particular use cases. It's worth noting > is that both components must provide interactive performance. I wonder if > there is some way to leverage

Re: Bug in CLJS compiler?

2012-10-27 Thread David Nolen
On Sat, Oct 27, 2012 at 8:19 AM, Tim wrote: > While playing around with a little test website I came across what, I > believe to be a bug in the CLJS compiler. It seems like the generation of > symbols for use in macros (e.g. var#) is broken when compiled into certain > JavaScript forms. > > Thi

Bug in CLJS compiler?

2012-10-27 Thread Tim
While playing around with a little test website I came across what, I believe to be a bug in the CLJS compiler. It seems like the generation of symbols for use in macros (e.g. var#) is broken when compiled into certain JavaScript forms. This is a bit of a contrived example but it illustrates t

Re: future with user specified ExecutorService

2012-10-27 Thread Max Penet
Yes I know, but my membership approval is still pending on clojure-dev (CA on the way), and from what I have read, I am supposed to ask first on the ML before creating a JIRA ticket. http://dev.clojure.org/display/design/JIRA+workflow Slow process... Max On Saturday, October 27, 2012 1:02:4

Re: future with user specified ExecutorService

2012-10-27 Thread Casper Clausen
+1 That would be nice. This may not be the right place for the suggestion though. On Thursday, October 25, 2012 2:43:58 PM UTC+2, Max Penet wrote: > > wrong commit: > https://github.com/mpenet/clojure/commit/9c6e47524dc21c6bdfaa9d0cc2a69377cc69cbf3 > > > On Thursday, October 25, 2012 2:35:01 P

Re: monads

2012-10-27 Thread Stephen Compall
On Fri, 2012-10-26 at 21:55 -0700, Ben Wolfson wrote: > f :: a -> b > g :: c -> d > h :: e -> j [renamed from "f"] > > and "you'd like to chain [them] like f(g(h(x))), but you can't because > b is a different type from c and d is a different type from e.", how > does m-chain help? > > I would hav