Passing data out of closure into the outer context

Greetings, I've stumbled across the following problem, which I believe is common and should have some sort of generic solution. Imagine I have ... ;; code inside defn ;; I extract some information out of my atom in closure: (swap! my-atom (fn [val] (let [extracted-info1 (extract-somethin

ClojureScript: how to get rid of "no longer a property access" warning

Hi, Executing legitimate code in CLJS REPL produces expected result with a warning. Is this syntax wrong? Is there a way to disable the warning? > (.getTime (js/Date.)) WARNING: The form (. (js/Date.) getTime) is no longer a property access. Maybe you meant (. (js/Date.) -getTime) instead? 1332

Re: Passing data out of closure into the outer context

Thanks, man! I ended up using atoms. On Tuesday, March 20, 2012 2:13:18 PM UTC-7, Cedric Greevey wrote: > > On Tue, Mar 20, 2012 at 11:16 AM, Tom Krestle > wrote: > > Greetings, > > > > I've stumbled across the following problem, which I believe is common

ClojureScript One: clojure-jack-in fails with "error in process filter" Symbol's value as variable is void: Type"

Hi folks, "clojure-jack-in" works quite well for regular clojure projects for me. I'm having hard time trying to figure out how to fix it for ClojureScript One project. Looking at *swank* buffer it looks like some random text is being inserted and attempted to evaluate as elisp and that causes

Multiple ClojureScript (sub)projects with shared CLJS libraries per single clojure project

Hi, The project I envision would consist of multiple completely independent conglomerates of CLJS scripts compiled into several separate final production .js with one single Clojure server. The reason for that is: 1. Smaller size of .js to load at each stage 2. Each time a browser transitions fr